Controlled token distribution to protect against malicious data and resource access

ABSTRACT

Techniques are described for controlling data and resource access. For example, methods and systems can facilitate controlled token distribution across systems and token processing in a manner so as to limit access to and to protect data that includes access codes.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. Ser. No. 16/927,745, filedJul. 13, 2020, which is a continuation of U.S. Ser. No. 16/421,925 filedMay 24, 2019, now U.S. Pat. No. 10,715,512, issued Jul. 14, 2020, whichis a continuation of U.S. Ser. No. 15/911,997 filed Mar. 5, 2018, nowU.S. Pat. No. 10,305,881, issued May 28, 2019, which is a continuationof U.S. Ser. No. 15/390,265, filed Dec. 23, 2016, now U.S. Pat. No.9,912,653, issued Mar. 6, 2018, which is a continuation-in-partapplication which claims the priority benefit under 35 USC 119(e) toeach of: (1) U.S. Ser. No. 14/973,205, filed on Dec. 17, 2015, now U.S.Pat. No. 9,807,096, issued Oct. 31, 2017, which claims priority to U.S.Provisional Application No. 62/093,828, filed on Dec. 18, 2014; (2) U.S.Ser. No. 12/435,972, filed on May 5, 2009, which claims priority to U.S.Provisional Application No. 61/050,543, filed May 5, 2008; and (3) U.S.Ser. No. 14/617,765, filed on Feb. 9, 2015, which is a continuation ofU.S. Ser. No. 14/289,010, filed May 28, 2014, now U.S. Pat. No.9,491,230, issued Nov. 8, 2016, which is a continuation of U.S. Ser. No.13/606,934, filed Sep. 7, 2012, now U.S. Pat. No. 8,775,519, issued Jul.8, 2014, which is a divisional application of U.S. Ser. No. 13/358,469,filed Jan. 25, 2012, now U.S. Pat. No. 8,266,211, issued Sep. 11, 2012,which is a divisional application of U.S. Ser. No. 12/204,648, filedSep. 4, 2008, now U.S. Pat. No. 8,126,991, issued Feb. 28, 2012, whichclaims priority to U.S. Provisional Application No. 60/969,884, filedSep. 4, 2007, the disclosures of each of the above-listed applicationsare incorporated by reference herein in their entirety for all purposes.

FIELD OF THE INVENTION

The present disclosure relates to controlling data and resource access,and in particular, to methods and systems for facilitating controlledtoken distribution across systems so as to limit access to and toprotect access codes.

BACKGROUND

Storing or transmitting data often presents a risk that a maliciousactor may use a device to access and/or use the data in an unauthorizedmanner. The larger a network grows in which particular data istransmitted, the higher this risk may be. However, such storage and/ortransmission is often critical to promoting desired resource usageand/or information distribution. Thus, there exists a problem as to howto accomplish desired information distribution and storage whilecontrolling data access to prevent unauthorized.

SUMMARY

In some embodiments, a system for generating and transmitting tokens forprocessing communications received from other devices over a network isprovided. A communication engine receives a first communication from asecond system, the first communication being associated with acredential and having been transmitted by the second system over awireless network; and transmits a second communication over the wirelessnetwork to the second system at a first time, the second communicationincluding a token. The communication also receives a third communicationfrom the second system, the third communication including the token andbeing received at a second time that is after the first time; and inresponse to a determination that the token corresponds to the secondsystem, transmits a fourth communication to the second system or to athird system, the fourth communication including an access-enabling codecorresponding to an access right for a resource. An authenticationengine authenticates the credential, the authentication indicating thatan entity associated with the second system is authorized to receivesecure tokens for facilitating resource access. A token engine, inresponse to the authentication, generates the token, the token beinggenerated based on or to correspond with each of: the entity and theresource; identifies that the resource corresponds to the token; anddetermines that the token corresponds to the second system.

In some embodiments, a computer-implemented method for generating andtransmitting tokens for processing communications received from otherdevices over a network is provided. A first communication is received ata first system, over a network and from a second system. The firstcommunication is associated with a credential; At the first system, thecredential is authenticated. The authentication indicates that an entityassociated with the second system is authorized to receive secure tokensfor facilitating resource access. In response to the authentication, atoken is generated at the first system based on or to correspond witheach of: the entity and a resource. A second communication istransmitted from the first system and over the wireless network to thesecond system at a first time, the second communication including thetoken. A third communication is received at the first system from thesecond system. The third communication includes the token and isreceived at a second time that is after the first time. The first systemidentifies that the resource corresponds to the token and determinesthat the token corresponds to the second system. In response todetermining that the token corresponds to the second system, a fourthcommunication is transmitted to the second system or to a third system.The fourth communication includes an access-enabling code correspondingto an access right for the resource.

In some embodiments, a computer-program product tangibly embodied in anon-transitory machine-readable storage medium, including instructionsconfigured to cause one or more data processors to perform actions thatinclude all or part of one or more processes or methods disclosedherein.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is described in conjunction with the appendedfigures:

FIG. 1 depicts a block diagram of an embodiment of a resourceaccess-facilitating interaction system;

FIG. 2 shows an illustration of hardware and network connections of aresource access-facilitating interaction system according to anembodiment of the invention;

FIG. 3 shows an illustration of a communication exchange betweencomponents involved in a resource access-facilitating interaction systemaccording to an embodiment of the invention;

FIG. 4 illustrates example components of a device;

FIG. 5 illustrates example components of resource access coordinatormodule;

FIG. 6 illustrates a flowchart of an embodiment of a process forassigning access rights for resources;

FIGS. 7A and 7B show embodiments of site systems in relations to mobiledevices;

FIG. 8 shows a block diagram of user device according to an embodiment;

FIG. 9 illustrates sample components of an embodiment of site system180, including connections to a NAS and access management system.

FIGS. 10A-10D illustrate examples of communication exchanges betweensystems involving identifications of tokens and access codes; and

FIG. 11 illustrates a flowchart of an embodiment of a process forconditionally transmitting access codes.

In the appended figures, similar components and/or features can have thesame reference label. Further, various components of the same type canbe distinguished by following the reference label by a dash and a secondlabel that distinguishes among the similar components. If only the firstreference label is used in the specification, the description isapplicable to any one of the similar components having the same firstreference label irrespective of the second reference label.

DETAILED DESCRIPTION

The ensuing description provides preferred exemplary embodiment(s) onlyand is not intended to limit the scope, applicability or configurationof the disclosure. Rather, the ensuing description of the preferredexemplary embodiment(s) will provide those skilled in the art with anenabling description for implementing a preferred exemplary embodiment.It is understood that various changes can be made in the function andarrangement of elements without departing from the spirit and scope asset forth in the appended claims.

The ensuing description provides preferred exemplary embodiment(s) onlyand is not intended to limit the scope, applicability or configurationof the disclosure. Rather, the ensuing description of the preferredexemplary embodiment(s) will provide those skilled in the art with anenabling description for implementing a preferred exemplary embodiment.It is understood that various changes can be made in the function andarrangement of elements without departing from the spirit and scope asset forth in the appended claims.

FIG. 1 depicts a block diagram of an embodiment of a resource managementsystem 100, according to an embodiment of the present disclosure. Mobiledevice 110 (which can be operated by a user 105) and an event-providerdevice 120 (which can be operated, controlled, or used by an eventprovider 115) can communicate with an access management system 185directly or via another system (e.g., via an intermediate system 150).Mobile device 110 may transmit data to access point 145, which isconnected to network 155, over communication channel 140 using antennae135. While FIG. 1 illustrates mobile device 110 communicating withaccess point 145 using a wireless connection (e.g., communicationchannel 140), in some embodiments, mobile device 110 may alsocommunicate with access point 145 using a wired connection (e.g., anEthernet connection). Mobile device 110 can also communicate with one ormore client devices, such as a client agent device 170 operated by aclient agent 175, a client register 160 or a client point device 165using a wired or wireless connection. In addition, using the accessmanagement system 185, an event provider 115 can identify an event, aparameter of attending the event, a date or dates of the event, alocation or locations of the event, etc. Each inter-system communicationcan occur over one or more networks 155 and can facilitate transmissionof a variety of types of data. It will be understood that, although onlyone of various systems, devices, entities and network are shown, theresource management system 100 can be extended to include multiple ofany given system(s), device(s), entity(ies), and/or networks.

Access management system 185 can be configured to manage a dynamic setof access rights to one or more resources. More specifically, accessmanagement system 185 can track which resources are to be made availableto users, specifications of the resources and times at which they willbe available. Access management system 185 can also allocate accessrights for resources and facilitate transmissions of notifications ofthe available rights to a set of user devices. For example, accessmanagement system 185 can alert users of the availability via a website,app page or email. As another example, access management system cantransmit data about access rights and resources to one or moreintermediate systems 150, which can facilitate distribution ofaccess-right availability and processing of requests for such rights.

Notifications of available access rights can be accompanied by optionsto request that one or more access rights be assigned to a user.Therefore, user 105 can provide input to mobile device 110 via aninterface to request such assignment and provide other pertinentinformation. Intermediate system 150 and/or access management system 185can process the request to ensure that the requested access right(s)remain available and that all required information has been receivedand, in some instances, verified. Thereafter, access management system185 can assign one or more access rights to the user, e.g., matching theaccess rights requested by the user.

Assigning an access right can include, for example, associating anidentifier of the right with an identifier of a user, changing a statusof the right from available to assigned, facilitating a cease innotifications that the access right is available, generating anaccess-enabling code to use such that the corresponding access will bepermitted and/or generating a notification to be received at mobiledevice 110 confirming the assignment and/or including data required forcorresponding access to be permitted.

In some instances, a resource is at least partly controlled, by aclient. The resource may be accessed at a particular location orstructure, and a variety of client devices may be present at thelocation so as to facilitate usage of an access right. Exemplary clientdevices can include client agent device 170, which can be one operatedby a client agent 175 (e.g., a human client agent), a client register160 (e.g., which can operate independently of an agent and/or can beconnected to or include a device that, while in a locked mode, canimpede resource access, such as a turnstile) and client point device 165(e.g., which can operate independently of an agent and/or can bepositioned at or around the resource-associated location. For example,in some instances client agent device 170 can be operated by an agent ata location for a resource that is an event (“event resource”) takingplace at the location. In this example, client agent device 170 is usedby an agent that is manning an entrance to the location (e.g., which caninclude, for example, a location of a structure or a geographic region)or a part thereof; client register 160 can be or can be connected to aturnstile, gate or lockable door that is positioned along a perimeter orentrance to a resource-associated location or part thereof; and clientpoint device 165 can be an electronic device positioned at or within aresource-associated location.

In some instances, mobile device 110 performs particular functions upondetecting a client device and/or the contrary. For example, mobiledevice 110 may locally retrieve or request (e.g., from an externalsource) an access-enabling code. The access-enabling code can betransmitted to the client device or a remote server (e.g., a serverhosting access management system 185) for evaluation and/or can belocally evaluated. The evaluation can include, for example, confirmingthat the access-enabling code has a particular characteristic or format(e.g., generally or one characteristic corresponding to a particularresource or type of access), matches one in an access-enabling code datastore and/or has not been previously redeemed. A result of theevaluation can be locally displayed at an evaluating device, can controla device component (e.g., a physical access control module), and/or canbe transmitted to another device, such as mobile device 110.

In some instances, user 105 can use multiple mobile devices 110 toperform various operations (e.g., using one device to request an accessright and another to interact with client devices). Some instances ofmobile device 110, access management system 185, intermediate system150, client agent device 170, client register 160 and/or client pointdevice 165 can include a portable electronic device (e.g., a smartphone, tablet, laptop computer or smart wearable device) or anon-portable electronic device (e.g., one or more desktop computers,servers and/or processors).

In exemplary embodiments, access rights can be represented in datamaintained at a client device or at access management system 185. Forexample, a database or data store include a list of identifiers for eachuser or user device having an assigned access right for a resource orassociating an identifier for each user or user device with anidentifier of a particular access right. In some instances, indicia canbe transmitted to a user device that indicates that an access right isavailed. In various instances, it may be permitted or prohibited for theindicia to be transferred. The indicia may be provided as part of anelectronic or physical object (e.g., a right to access an event) orindependently. The indicia may include an access-enabling code.

In some instances, access management system 185 communicates with one ormore intermediate systems 150, each of which may be controlled by adifferent entity as compared to an entity controlling access managementsystem 185. For example, access management system 185 may assign accessrights to intermediate systems 150 (e.g., upon acceptance of terms).Intermediate system 150 can then collect data pertaining to the assignedaccess rights and/or a corresponding event, can format and/or edit thedata, generate a notification of availability of the access rights thatincludes the formatted and/or edited data and facilitate presentation ofthe notification at a mobile device 110. When intermediate system 150receives a communication from the mobile device 110 indicative of anaccess-right request, intermediate system 150 can facilitate assignment(or reassignment) of an access right to the user (e.g., by transmittingrelevant information to access management system 185 identifying theuser and/or user device and/or by transmitting relevant information tomobile device 110 pertaining to the access right).

A resource can include one managed or provided by a client, such as aperforming entity or an entity operating a venue. A mobile device 110can transmit data corresponding to the access right (e.g., anaccess-enabling code) to a client device upon, for example, detectingthe client device, detecting that a location of the mobile device 110 iswithin a prescribed geographical region, or detecting particular input.The receiving client device may include, for example, a client agentdevice 170 operated at an entrance of a defined geographical location ora client register 160 that includes or is attached to a lockingturnstile. The client device can then analyze the code to confirm itsvalidity and applicability for a particular resource and/or access type,and admittance to the event can be accordingly permitted. For example, aturnstile may change from a locked to an unlocked mode upon confirmationof the code's validity and applicability.

Each of the depicted devices and/or systems may include a software agentor application (“app”) that, when executed, performs one or more actionsas described herein. In some instances, a software agent or app on onedevice is, at least in part, complementary to a software agent or app onanother device (e.g., such that a software agent or app on mobile device110 is, at least in part, complementary to at least part of one onaccess management system 185 and/or a client device; and/or such that asoftware agent or app on intermediate system 150 is, at least in part,complementary to at least part of one on access management system 185).

In some instances, a network in the one or more networks 155 can includean open network, such as the Internet, personal area network, local areanetwork (LAN), campus area network (CAN), metropolitan area network(MAN), wide area network (WAN), wireless local area network (WLAN), aprivate network, such as an intranet, extranet, or other backbone. Insome instances, a network in the one or more networks 155 includes ashort-range communication channel, such as Bluetooth or Bluetooth LowEnergy channel. Communicating using a short-range communication such asBLE channel can provide advantages such as consuming less power, beingable to communicate across moderate distances, being able to detectlevels of proximity, achieving high-level security based on encryptionand short ranges, and not requiring pairing for inter-devicecommunications.

In one embodiment, communications between two or more systems and/ordevices can be achieved by a secure communications protocol, such assecure sockets layer (SSL), transport layer security (TLS). In addition,data and/or transactional details may be encrypted based on anyconvenient, known, or to be developed manner, such as, but not limitedto, DES, Triple DES, RSA, Blowfish, Advanced Encryption Standard (AES),CAST-128, CAST-256, Decorrelated Fast Cipher (DFC), Tiny EncryptionAlgorithm (TEA), eXtended TEA (XTEA), Corrected Block TEA (XXTEA),and/or RC5, etc.

It will be appreciated that, while a variety of devices and systems areshown in FIG. 1 , in some instances, resource management system 100 caninclude fewer devices and/or systems. Further, some systems and/ordevices can be combined. For example, a client agent device 170 may alsoserve as an access management system 185 or intermediate system 150 soas to as to facilitate assignment of access rights.

As described in further detail herein, an interaction between mobiledevice 110 and a client device (e.g., client agent device 170, clientregister 160 or client point device 165) can facilitate, for example,verification that user 105 has a valid and applicable access right,obtaining an assignment of an access right, and/or obtaining anassignment of an upgraded access right.

In addition, mobile device 110-2, which is operated by user 125-2, mayinclude a user device that is located at a stadium or concert hallduring an event. Mobile device 110-2 may directly interact with a clientdevice (e.g., client agent device 170, client register 160 or clientpoint device 165), which is also located at the stadium or concert hallduring the event. As such, the access management system 185 may beupdated or accessed by mobile device 110-2 via the client agent device170. For example, mobile device 110-2 may communicate with the clientagent device 170 over a short-range communication channel 190, such asBluetooth or Bluetooth Low Energy channel, Near Field Communication(NFC), Wi-Fi, RFID, Zigbee, ANT, etc. Communicating using a short-rangecommunication such as BLE channel can provide advantages such asconsuming less power, being able to communicate across moderatedistances, being able to detect levels of proximity, achievinghigh-level security based on encryption and short ranges, and notrequiring pairing for inter-device communications. After the short-rangecommunication link 190 is established, mobile device 110-2 maycommunicate with the access management system 185 and access the item oritems of resources. That is, while mobile device B is configured tocommunicate over network 155, mobile device 110-2 may communicate withthe access management system 185 via the client agent device 170,instead of the network 155.

It will be appreciated that various parts of system 100 can begeographically separated. It will further be appreciated that system 100can include a different number of various components rather than anumber depicted in FIG. 1 . For example, two or more of accessassignment systems 185; one or more site systems 180; and intermediatesystem 150 may be located in different geographic locations (e.g.,different cities, states or countries).

FIG. 2 shows an illustration of hardware and network connections of aresource access-facilitating interaction system 200 according to anembodiment of the invention. Each of various user devices 210-1, 210-2,210-3, 210-4 and 210-5 can connect, via one or more inter-networkconnection components (e.g., a router 212) and one or more networks 270to a primary assignment management system 214 or a secondary assignmentmanagement system 216-1, 216-2 or 216-3.

Primary assignment management system 214 can be configured to coordinateand/or control initial assignment of access rights. Secondary assignmentmanagement system 216 can be configured to coordinate and/or controlreassignment and/or transfer of access rights (e.g., from one user oruser device to another or from an intermediate agent to a user or userdevice). Such transfer may occur as a result of a sale or fee payment.Secondary assignment management system 216 may also manage transferoffers (e.g., to allow a first user to identify a price at which atransfer request would be granted and to detect if a valid request isreceived). It will be appreciated that, although primary assignmentmanagement system 214 is shown to be separate from each secondaryassignment management system 216, in some instances, an assignmentmanagement system may relate to both a primary and secondary channel,and a single data store or a localized cluster of data stores mayinclude data from both channels.

Each of primary access assignment system 214 and secondary accessassignment system 216 can include a web server 218 that processes andresponds to HTTP requests. Web server 218 can retrieve and deliverweb-page data to a user device 210 that, for example, identify aresource, identify a characteristic of each of one or more access rightsfor the resource, include an invitation to request assignment of anaccess right, facilitate establishment or updating of an account, and/oridentify characteristics of one or more assigned access rights. Webserver 218 can be configured to support server-side scripting and/orreceive data from user devices 210, such as data from forms or fileuploads.

In some instances, a web server 218 can be configured to communicatedata about a resource and an indication that access rights for theresource are available. Web server 218 can receive a requestcommunication from a user device 210 that corresponds to a request forinformation about access rights. The request can include one or moreconstraints, which can correspond to (for example) values (e.g., to bematched or to define a range) of particular fields.

A management server 222 can interact with web server 218 to provideindications as to which access rights' are available for assignment,characteristics of access rights and/or what data is needed to assign anaccess right. When requisite information is received (e.g., about a userand/or user device, identifying a final request for one or more accessrights, including payment information, and so on), management server 222can coordinate an assignment of the one or more access rights. Thecoordination can include updating an access-right data store to change astatus of the one or more access rights (e.g., to assigned); toassociate each of the one or more access rights with a user and/or userdevice; to generate or identify one or more access-enabling codes forthe one or more access rights; and/or to facilitate transmissionreflecting the assignment (e.g., and including the one or moreaccess-enabling codes) to a user device.

Management server 222 can query, update and manage an access-right datastore to identify access rights' availability and/or characteristicand/or to reflect a new assignment. The data store can include oneassociated with the particular assignment system. In some instances, thedata store includes incomplete data about access rights for a resource.For example, a data store 224 at and/or used by a secondary accessassignment system 216 may include data about an incomplete subset ofaccess rights that have been allocated for a particular resource. Toillustrate, a client agent may have indicated that an independentintermediary system can (exclusively or non-exclusively) coordinateassignment of a portion of access rights for a resource but not theremainder. A data store 224 may then, for example, selectively includeinformation (e.g., characteristics, statuses and/or assignmentassociations) for access rights in the portion.

Data store 224 or 226 associated with a particular primary or secondaryaccess assignment system can include assignment data for a set of accessrights that are configured to be set by the particular primary orsecondary access assignment system or by another system. For example, arule can indicate that a given access right is to have an availablestatus until a first of a plurality of access assignment systems assignsthe access right. Accordingly, access assignment systems would then needto communicate to alert each other of assignments.

In one instance, management server 222 (or another server in an accessassignment system) sends a communication to a central data managementserver farm 228 reflecting one or more recent assignments. Thecommunication may include an identification of one or more accessrights, an indication that the access right(s) have been assigned, anidentification of a user and/or user device associated with theassignment and/or one or more access-enabling codes generated oridentified to be associated with the assignment. The communication canbe sent, for example, upon assigning the access right(s), as a precursorto assigning the access right(s) (e.g., to confirm availability and/orrequest assignment authorization), at defined times or time intervalsand/or in response to an assignment-update request received from datamanagement server farm 228.

Data management server farm 228 can then update a central data store toreflect the data from the communication. The central data store can bepart of, for example, a network-attached storage 232 and/or astorage-area network 234.

In some instances, a data store 224 or 226 can include a cache, thatincludes data stored based on previous communications with datamanagement server farm 228. For example, data management server farm 228may periodically transmit statuses of a set of access rights (e.g.,those initially configured to be assignable by an access assignmentsystem) or an updated status (e.g., indicating an assignment) of one ormore access rights. As another example, data management server farm 228may transmit statuses upon receiving a request from an access assignmentsystem for statuses and/or authorization to assign one or more accessrights.

An access assignment system may receive statuses less frequently or attimes unaligned with requests received from user devices requestinginformation about access rights and/or assignments. Rather than initiatea central data store query responsive to each user-device request, amanagement server 222 can rely on cached data (e.g., locally cacheddata) to identify availability of one or more access rights, as reflectin webpage data and/or communications responsive to requestcommunications for access-right information. After requisite informationhas been obtained, management server 222 can then communicate with datamanagement server farm 228 to ensure that one or more particular accessrights have remained available for assignment.

In some instances, one or more of primary access assignment system 214and/or a secondary access assignment system 214 need not include a localor system-inclusive data store for tracking access-right statuses,assignments and/or characteristics. Instead, the access assignmentsystem may communicate with a remote and/or central data store (e.g.,network-attached storage 232 or storage-area network 234).

Access management system 120 can include a primary access assignmentsystem 214 and/or a secondary access assignment system 214; datamanagement server farm 228; and/or a central data store (e.g.,network-attached storage 232 or storage-area network 234). Each of oneor more intermediate systems 130 can include a primary access assignmentsystem 214 and/or a secondary access assignment system 214.

Data management server farm 228 may periodically and/or routinely assessa connection with an access assignment system 214. For example, a testcommunication can be sent that is indicative of a request to respond(e.g., with particular data or generally). If a response communicationis not received, if a response communication is not received within adefined time period and/or if a response communication includesparticular data (e.g., reflecting poor data integrity, network speed,processing speed, etc.), data management server farm 228 may reconfigureaccess rights and/or permissions and/or may transmit anothercommunication indicating that assignment rights of the access assignmentsystem are limited (e.g., to prevent the system from assigning accessrights).

It will be appreciated that various parts of system 200 can begeographically separated. For example, two or more of primary accessassignment system 214; one or more of secondary access assignmentsystems 214; and data management server farm 228 may be located indifferent geographic locations (e.g., different cities, states orcountries).

It will further be appreciated that system 200 can include a differentnumber of various components rather than a number depicted in FIG. 2 .For example, system 200 can include multiple data management serverfarms 228, central data stores and/or primary access assignment systems214 (e.g., which can be geographically separated, such as being locatedin different cities, states or countries). In some instances, processingmay be split (e.g., according to a load-balancing technique) acrossmultiple data management server farms 228 and/or across multiple accessassignment systems 214. Meanwhile, the farms and/or systems can beconfigured to accept an increased or full load should another farmand/or system be unavailable (e.g., due to maintenance). Data stored ina central data store may also be replicated in geographically separateddata stores.

FIG. 3 shows an illustration of a communication exchange betweencomponents involved in a resource access-facilitating interaction system300 according to an embodiment of the invention. A user device 310 cansend one or more HTTP requests to a web-server system 318, andweb-server system 318 can respond with one or more HTTP responses thatinclude webpage data. The webpage data can include, for example,information about one or more resources, characteristics of a set ofaccess rights for each of the one or more resources, availability of oneor more access rights, an invitation to request an assignment of one ormore access rights and/or indications as to what information is requiredfor an access-right assignment. HTTP requests can includeassignment-request data (e.g., a resource identification, requisiteinformation, and/or an identification of an access-right constraint oraccess right).

Web-server system 318 can include one or more web processors (e.g.,included in one or more server farms, which may be geographicallyseparated) to, for example, map a path component of a URL to web data(e.g., stored in a local file system or generated by a program);retrieve the web data; and/or generate a response communicationincluding the web data. Web processor can further parse communication toidentify input-corresponding data in HTTP requests, such as field valuesrequired for an access-right assignment.

Web-server system 318 can also include a load balancer to distributeprocessing tasks across multiple web processors. For example, HTTPrequests can be distributed to different web processors. Load-balancingtechniques can be configured so as, for example, to distributeprocessing across servers or server farms, decrease a number of hopsbetween a web server and user device, decrease a geographical locationbetween a user device and web server, etc.

Web-server system 318 can further include a RAID component, such as aRAID controller or card. A RAID component can be configured, forexample, to stripe data across multiple drives, distribute parity acrossdrives and/or mirror data across multiple drives. The RAID component canbe configured to improve reliability and increase request-processingspeeds.

Web-server system 318 can include one or more distributed,non-distributed, virtual, non-virtual, local and/or remote data stores.The data stores can include web data, scripts and/or content object(e.g., to be presented as part or web data).

Some HTTP requests include requests for identifications ofresource-access characteristics and/or availability. To provide web datareflecting such information, web-server system 318 can request theinformation from another server, such as an SQL system 341 (e.g., whichmay include one or more servers or one or more server farms).

SQL system 341 can include one or more SQL processors (e.g., included inone or more server farms, which may be geographically separated). SQLprocessors can be configured to query, update and otherwise use one ormore relational data stores. SQL processors can be configured to execute(and, in some instances, generate) code (e.g., SQL code) to query arelational data store.

SQL system 341 can include a database engine, that includes a relationalengine, OLE database and storage engine. A relational engine canprocess, parse, compile, and/or optimize a query and/or makequery-associated calls. The relational engine can identify an OLE DB rowset that identifies the row with columns matching search criteria and/ora ranking value. A storage engine can manage data access and use therowset (e.g., to access tables and indices) to retrieve query-responsivedata from one or more relational databases.

SQL system 341 can include one or more distributed, non-distributed,virtual, non-virtual, local and/or remote relational data stores. Therelational databases can include linked data structures identifying, forexample, resource information, access-right identifications andcharacteristics, access-right statuses and/or assignments, and/or userand/or user account data. Thus, for example, use of the relationalstructures may facilitate identifying, for a particular user, acharacteristic of an assigned access right and information about aresource associated with the access right.

One or more data structures in a relational data structure may reflectwhether particular access rights have been assigned or remain available.This data may be based on data received from a catalog system 342 thatmonitors and tracks statuses of resource access rights. Catalog system342 can include one or more catalog processors (e.g., included in one ormore server farms, which may be geographically separated). Catalogprocessors can be configured to generate status-update requestcommunications to be sent to one or more access assignment systemsand/or intermediate systems and/or to receive status-updatecommunications from one or more access assignment systems and/orintermediate systems. A status-update communication can, for example,identify an access right and/or resource and indicate an assignment ofthe access right. For example, a status-update communication canindicate that a particular access right has been assigned and is thus nolonger available. In some instances, a status-update communicationidentifies assignment details, such as a user, account and/or userdevice associated with an access-right assignment; a time that theassignment was made; and/or a price associated with the assignment.

In some instances, a status update is less explicit. For example, acommunication may identify an access right and/or resource and request afinal authorization of an assignment of the access right. Catalog system342 can then verify that the access right is available for assignment(e.g., and that a request-associated system or entity is authorized tocoordinate the assignment) and can transmit an affirmative response.Such a communication exchange can indicate (in some instances) that theaccess right is assigned and unavailable for other assignment.

In some instances, catalog system 342 can also be integrated with anon-intermediate access assignment system, such that it can directlydetect assignments. For example, an integrated access assignment systemcan coordinate a message exchange with a user device, can query acatalog data store to identify available access rights and canfacilitate or trigger a status-change of an access right to reflect anassignment (e.g., upon having received all required information.

Whether a result of a direct assignment detection or a status updatefrom an intermediate system, a database engine of catalog system 342 canmanage one or more data stores so as to indicate a current status ofeach of a set of access rights for a resource. The one or more datastores may further identify any assignment constraints. For example,particular access rights may be earmarked so as to only allow one ormore particular intermediate systems to trigger a change to the accessrights' status and/or to assign the access rights.

The database engine can include a digital asset management (DAM) engineto receive, transform (e.g., annotate, reformat, introduce a schema,etc.) status-update communications, and identify other data (e.g., anidentifier of an assigning system and/or a time at which a communicationwas received) to associate with a status update (e.g., an assignment).Therefore, the DAM engine can be configured to prepare storage-updatetasks so as to cause a maintained data store to reflect a recent datachange.

Further, the DAM engine can facilitate handling of data-store queries.For example, a status-request communication or authorization-requestcommunication can be processed to identify variables and/or indices touse to query a data store. A query can then be generated and/or directedto a data store based on the processing. The DAM engine can relay (e.g.,and, potentially, perform intermediate processing to) a query result toa request-associate system.

The database engine can also include a conflict engine, which can beconfigured to access and implement rules indicating how conflicts are tobe handled. For example, catalog system 342 may receive multiplerequests within a time period requesting an assignment authorization (ora hold) for a particular access right. A rule may indicate that a firstrequest is to receive priority, that a request associated with a morehighly prioritized requesting system (e.g., intermediate system) is tobe prioritized, that a request associated with a relatively high (orlow) quantity of access rights identified in the request for potentialassignment are to be prioritized, etc.

The database engine can further include a storage engine configured tomanage data access and/or data updates (e.g., modifying existing data oradding new data). The data managed by and/or accessible to the storageengine can be included in one or more data stores. The data stores caninclude, for example, distributed, non-distributed, virtual,non-virtual, local and/or remote data stores. The data stores caninclude, for example, a relational, non-relational, object, non-object,document and/or non-document data store. Part or all of a data store caninclude a shadow data store, that shadows data from another data store.Part or all of a data store can include an authoritative data store thatis (e.g., directly and/or immediately) updated with access-rightassignment changes (e.g., such that a primary or secondary accessassignment system updates the data store as part of an access-rightassignment process, rather than sending a post-hoc status-updatecommunication reflecting the assignment). In some instances, a datastore an authoritative data store identifies a status for each of a set(e.g., or all) of access rights for a given resource. Should there beany inconsistency between an authoritative data store and another datastore (e.g., at an intermediate system), system 300 can be configuredsuch that the authoritative data store is controlling.

System 300 can further include a replication system 343. Replicationsystem 343 can include one or more replication processors configured toidentify new or modified data, to identify one or more data storesand/or location at which to store the new or modified data and/or tocoordinate replication of the data. In some instances, one or more ofthese identifications and/or coordination can be performed using areplication rule. For example, a replication rule may indicate thatreplication is to be performed in a manner biased towards storingreplicated data at a data store geographically separated from anotherdata store storing the data.

A data duplicator can be configured to read stored data and generate oneor more write commands so as to store the data at a different datastore. A controller can manage transmitting write commands appropriatelyso as to facilitate storing replicated data at identified data stores.Further, a controller can manage data stores, such as a distributedmemory or distributed shared memory, to ensure that a currently activeset of data stores includes a target number of replications of data.

Accordingly, web-server system 318 can interact with user device 310 toidentify available access rights and to collect information needed toassign an access right. Web-server system 318 can interact with SQLsystem 341 so as to retrieve data about particular resources and/oraccess rights so as to configure web data (e.g., via dynamic webpages orscripts) to reflect accurate or semi-accurate information and/orstatuses. SQL system 341 can use relational data stores to quicklyprovide such data. Meanwhile, catalog system 342 may manage one or morenon-relational and/or more comprehensive data stores may be tasked withmore reliably and quickly tracking access-right statuses andassignments. The tracking may include receiving status updates (e.g.,via a push or pull protocol) from one or more intermediate systemsand/or by detecting assignment updates from non-intermediate systems,such as an integrated access assignment system and/or SQL system 341.Catalog system 342 may provide condensed status updates (e.g.,reflecting a binary indication as to whether an access right isavailable) to SQL system 341 periodically, at triggered times and/or inresponse to a request from the SQL system. A replication system 343 canfurther ensure that data is replicated at multiple data stores, so as toimprove a reliability and speed of system 300.

It will be appreciated that various parts of system 300 can begeographically separated. For example, each of user device 310,intermediate system 330, web-server system 318, SQL system 341, catalogsystem 342 and replication 343 may be located in different geographiclocations (e.g., different cities, states or countries).

FIG. 4 illustrates example components of a device 400, such as a clientdevice (e.g., client agent device 140, client register 150 and/or clientpoint device 160), an intermediate system (e.g., intermediate system130) and/or an access management system (e.g., access management system120) according to an embodiment of the invention.

The components can include one or more modules that can be installed ondevice 400. Modules can include some or all of the following: a networkinterface module 402 (which can operate in a link layer of a protocolstack), a message processor module 404 (which can operate in an IP layerof a protocol stack), a communications manager module 406 (which canoperate in a transport layer of a protocol stack), a communicationsconfigure module 408 (which can operate in a transport and/or IP layerin a protocol stack), a communications rules provider module 410 (whichcan operate in a transport and/or IP layer in a protocol stack),application modules 412 (which can operate in an application layer of aprotocol stack), a physical access control module 432 and one or moreenvironmental sensors 434.

Network interface module 402 receives and transmits messages via one ormore hardware components that provide a link-layer interconnect. Thehardware component(s) can include, for example, RF antenna 403 or a port(e.g., Ethernet port) and supporting circuitry. In some embodiments,network interface module 402 can be configured to support wirelesscommunication, e.g., using Wi Fi (IEEE 802.11 family standards),Bluetooth® (a family of standards promulgated by Bluetooth SIG, Inc.),BLE, or near-field communication (implementing the ISO/IEC 18092standards or the like).

RF antenna 403 can be configured to convert electric signals into radioand/or magnetic signals (e.g., to radio waves) to transmit to anotherdevice and/or to receive radio and/or magnetic signals and convert themto electric signals. RF antenna 403 can be tuned to operate within aparticular frequency band. In some instances, a device includes multipleantennas, and the antennas can be, for example, physically separated. Insome instances, antennas differ with respect to radiation patterns,polarizations, take-off angle gain and/or tuning bands. RF interfacemodule 402 can include one or more phase shifters, filters, attenuators,amplifiers, switches and/or other components to demodulate receivedsignals, coordinate signal transmission and/or facilitate high-qualitysignal transmission and receipt.

In some instances, network interface module 402 includes a virtualnetwork interface, so as to enable the device to utilize an intermediatedevice for signal transmission or reception. For example, networkinterface module 402 can include VPN software.

Network interface module 402 and one or more antennas 403 can beconfigured to transmit and receive signals over one or more connectiontypes. For example, network interface module 402 and one or moreantennas 403 can be configured to transmit and receive WiFi signals,cellular signals, Bluetooth signals, Bluetooth Low Energy (BLE) signals,Zigbee signals, or Near-Field Communication (NFC) signals.

Message processor module 404 can coordinate communication with otherelectronic devices or systems, such as one or more servers or a userdevice. In one instance, message processor module 404 is able tocommunicate using a plurality of protocols (e.g., any known, futureand/or convenient protocol such as, but not limited to, XML, SMS, MIMS,and/or email, etc.). Message processor module 404 may further optionallyserialize incoming and/or outgoing messages and facilitate queuing ofincoming and outgoing message traffic.

Message processor module 404 can perform functions of an IP layer in anetwork protocol stack. For example, in some instances, messageprocessor module 404 can format data packets or segments, combine datapacket fragments, fragment data packets and/or identify destinationapplications and/or device addresses. For example, message processormodule 404 can defragment and analyze an incoming message to determinewhether it is to be forwarded to another device and, if so, can addressand fragment the message before sending it to the network interfacemodule 402 to be transmitted. As another example, message processormodule 404 can defragment and analyze an incoming message to identify adestination application that is to receive the message and can thendirect the message (e.g., via a transport layer) to the application.

Communications manager module 406 can implement transport-layerfunctions. For example, communications manager module 406 can identify atransport protocol for an outgoing message (e.g., transmission controlprotocol (TCP) or user diagram protocol (UDP)) and appropriatelyencapsulate the message into transport protocol data units. Messageprocessor module 404 can initiate establishment of connections betweendevices, monitor transmissions failures, control data transmission ratesand monitoring transmission quality. As another example, communicationsmanager module 406 can read a header of an incoming message to identifyan application layer protocol to receive the message's data. The datacan be separated from the header and sent to the appropriateapplication. Message processor module 404 can also monitor the qualityof incoming messages and/or detect out of order incoming packets.

In some instances, characteristics of message-receipt ormessage-transmission quality can be used to identify a health status ofan established communications link. In some instances, communicationsmanager module 406 can be configured to detect signals indicating thehealth status of an established communications link (e.g., a periodicsignal from the other device system, which if received without dropouts,indicates a healthy link).

In some instances, a communication configurer module 408 is provided totrack attributes of another system so as to facilitate establishment ofa communication session. In one embodiment, communication configurermodule 408 further ensures that inter-device communications areconducted in accordance with the identified communication attributesand/or rules. Communication configurer module 408 can maintain anupdated record of the communication attributes of one or more devices orsystems. In one embodiment, communications configurer module 408 ensuresthat communications manager module 406 can deliver the payload providedby message processor module 404 to the destination (e.g., by ensuringthat the correct protocol corresponding to the client system is used).

A communications rules provider module 410 can implement one or morecommunication rules that relate to details of signal transmissions orreceipt. For example, a rule may specify or constrain a protocol to beused, a transmission time, a type of link or connection to be used, adestination device, and/or a number of destination devices. A rule maybe generally applicable or conditionally applicable (e.g., only applyingfor messages corresponding to a particular app, during a particular timeof day, while a device is in a particular geographical region, when ausage of a local device resource exceeds a threshold, etc.). Forexample, a rule can identify a technique for selecting between a set ofpotential destination devices based on attributes of the set ofpotential destination devices as tracked by communication configuremodule 408. To illustrate, a device having a short response latency maybe selected as a destination device. As another example, communicationsrules provider 410 can maintain associations between various devices orsystems and resources. Thus, messages corresponding to particularresources can be selectively transmitted to destinations having accessto such resources.

A variety of application modules 412 can be configured to initiatemessage transmission, process incoming transmissions, facilitateselective granting of resource access, facilitate processing of requestsfor resource access, and/or performing other functions. In the instancedepicted in FIG. 4 , application modules 412 include an auto-updatermodule 414, a resource access coordinator module 416, and/or a codeverification module 418.

Auto-updater module 414 automatically updates stored data and/or agentsoftware based on recent changes to resource utilization, availabilityor schedules and/or updates to software or protocols. Such updates canbe pushed from another device (e.g., upon detecting a change in aresource availability or access permit) or can be received in responseto a request sent by device 400. For example, device 400 can transmit asignal to another device that identifies a particular resource, and aresponsive signal can identify availabilities of access to the resource(e.g., available seat reservations for a sporting event or concert). Asanother example, device 400 can transmit a signal that includes anaccess access-enabling code, and a responsive signal can indicatewhether the code is applicable for access of a particular resourceand/or is valid.

In some instances, auto-updater module 414 is configured to enable theagent software to understand new, messages, commands, and/or protocols,based on a system configuration/change initiated on another device.Auto-updater module 414 may also install new or updated software toprovide support and/or enhancements, based on a system configurationchange detected on device 400. System configuration changes that wouldnecessitate changes to the agent software can include, but are notlimited to, a software/hardware upgrade, a security upgrade, a routerconfiguration change, a change in security settings, etc. For example,if auto-updater module 414 determines that a communication link withanother device has been lost for a pre-determined amount of time,auto-updater module 414 can obtain system configuration information tohelp re-establish the communication link. Such information may includenew settings/configurations on one or more hardware devices or new orupgraded software on or connected to device 400. Thus, auto-updatermodule 414 can detect or be informed by other software when there is anew version of agent software with additional functionality and/ordeficiency/bug corrections or when there is a change with respect to thesoftware, hardware, communications channel, etc.), and perform updatesaccordingly.

Based on the newly obtained system configuration for device 400,auto-updater module 414 can cause a new communication link to bere-established with another device. In one embodiment, uponestablishment of the communication link, system configurationinformation about device 400 can also be provided to another device tofacilitate the connection to or downloading of software to device 400.

In one embodiment, when a poor health signal is detected by anotherdevice (e.g., when the health signal is only sporadically received butthe communication link is not necessarily lost), the other device cansend a command to auto-updater module 414 to instruct auto-updatermodule 414 to obtain system configuration information about device 400.The updated system configuration information may be used in an attemptto revive the unhealthy communications link (e.g., by resending aresource request). For example, code can utilize appropriate systemcalls for the operating system to fix or reestablish communications. Byway of example and not limitation, model and driver information isoptionally obtained for routers in the system in order querying them. Byway of further example, if the code determines that a new brand ofrouter has been installed, it can adapt to that change, or to the changein network configuration, or other changes.

Instead or in addition, the host server (e.g., via communicationsmanager 406) can send specific instructions to auto-updater module 414to specify tests or checks to be performed on device 400 to determinethe changes to the system configurations (e.g., by automaticallyperforming or requesting an inventory check of system hardware and/orsoftware). For example, the components involved in the chain of hopsthrough a network can be queried and analyzed. Thus, for example, if anew ISP (Internet service provider) is being used and the managementsystem traffic is being filtered, or a new router was installed and thesoftware needs to change its configuration, or if someone made a changeto the operating system that affects port the management system is usingto communicate, the management system (or operator) can communicate withthe ISP, change it back, or choose from a new available port,respectively.

The specific tests may be necessary to help establish the communicationlink, if, for example, the automatic tests fail to provide sufficientinformation for the communication link to be re-established, ifadditional information is needed about a particular configurationchange, and/or if the client system is not initially supported by theauto-updater module 414, etc.

Auto-updater module 414 can also receive signals identifying updatespertaining to current or future availability of resources and/or accesspermits. Based on the signals, auto-updater module 414 can modify, addto or delete stored data pertaining to resource availabilities, resourceschedules and/or valid access permits. For example, upon receiving anupdate signal, auto-updater 414 can modify data stored in one or moredata stores 422, such as an account data store 424, resourcespecification data store 426, resource status data store 428 and/oraccess-enabling code data store 430.

Account data store 424 can store data for entities, such asadministrators, intermediate-system agents and/or users. The accountdata can include login information (e.g., username and password),identifying information (e.g., name, residential address, phone number,email address, age and/or gender), professional information (e.g.,occupation, affiliation and/or professional position), preferences(e.g., regarding event types, performers, seating areas, and/or resourcetypes), purchase data (e.g., reflecting dates, prices and/or items ofpast purchases) and/or payment data (e.g., credit card number andexpiration date or payment account information). The account data canalso or alternatively include technical data, such a particular entitycan be associated with one or more device types, IP addresses, browseridentifier and/or operating system identifier).

Resource specification data store 426 can store specification datacharacterizing each of one or more resources. For example, specificationdata for a resource can include a processing power, available memory,operating system, compatibility, device type, processor usage, powerstatus, device model, number of processor cores, types of memories, dateand time of availability, a performing entity, a venue of the eventand/or a set of seats (e.g., a chart or list). Specification data canfurther identify, for example, a cost for each of one or more accessrights.

Resource status data store 428 can store status data reflecting whichresources are available (or unavailable), thereby indicating whichresources have one or more open assignments. In some instances, thestatus data can include schedule information about when a resource isavailable. Status data can include information identifying an entity whorequested, reserved or was assigned a resource. In some instances,status information can indicate that a resource is being held orreserved and may identify an entity associated with the hold or reserveand/or a time at which the hold or reservation will be released.

Access-enabling code data store 430 can store access-enabling code datathat includes one or more codes and/or other information that can beused to indicate that an entity is authorized to use, have or receive aresource. An access-enabling code can include, for example, a numericstring, an alphanumeric string, a text string, a 1-dimensional code, a2-dimensional code, a barcode, a quick response (QR) code, an image, astatic code and/or a temporally dynamic code. An access-enabling codecan be, for example, unique across all instances, resource types and/orentities. For example, access-enabling codes provided in association fortickets to a particular event can be unique relative to each other. Insome instances, at least part of a code identifies a resource orspecification of a resource. For example, for a ticket to a concert,various portions of a code may reflect: a performing entity, resourcelocation, date, section and access-permitted location identifier.

One or more of data stores 424, 426, 428, and 430 can be a relationaldata store, such that elements in one data store can be referencedwithin another data store. For example, resource status data store 428can associate an identifier of a particular ticket with an identifier ofa particular entity. Additional information about the entity can then beretrieved by looking up the entity identifier in account data store 424.

Updates to data stores 424, 426, 428, and 430 facilitated and/orinitiated by auto-updater module 414 can improve cross-device dataconsistency. Resource access coordinator module 416 can coordinateresource access by, for example, generating and distributingidentifications of resource availabilities; processing requests forresource access; handling competing requests for resource access; and/orreceiving and responding to resource-offering objectives.

FIG. 5 illustrates example components of resource access coordinatormodule 416 that may operate, at least in part, at an access managementsystem (e.g., access management system) according to an embodiment ofthe invention. A resource specification engine 502 can identify one ormore available resources. For example, resource specification engine 502can detect input that identifies a current or future availability of anew resource.

Resource specification engine 502 can identify one or morespecifications of each of one or more resources. A specification caninclude an availability time period. For example, resource specificationengine 502 can determine that a resource is available, for example, at aparticular date and time (e.g., as identified based on input), for atime period (e.g., a start to end time), as identified in the input,and/or from a time of initial identification until another inputindicating that the resource is unavailable is detected. A specificationcan also or alternatively include a location (e.g., a geographiclocation and/or venue) of the resource. A specification can also oralternatively include one or more parties associated with the resource(e.g., performing acts or teams). Resource specification engine 502 canstore the specifications in association with an identifier of theresource in resource specifications data store 426.

A resource-access allocation engine 504 can allocate access rights forindividual resources. An access right can serve to provide an associatedentity with the right or a priority to access a resource. Because (forexample) association of an access right with an entity can, in someinstances, be conditioned on fee payment or authorization thereof, anallocated access right can be initially unassociated with particularentities (e.g., users). For example, an allocated right can correspondto one or more access characteristics, such as an processor identifier,a usage time, a memory allocation, a geographic location (e.g., sectionor seat identifier), and/or a fee. For an allocated access right,resource-access allocation engine 504 can store an identifier of theright in resource statuses data store 428 in association with anidentifier for the resource and an indication that it has not yet beenassigned to a particular entity.

A communication engine 506 can facilitate communicating the availabilityof the resource access rights to users. In some instances, a publisherengine 508 generates a presentation that identifies a resource andindicates that access rights are available. Initially or in response touser interaction with the presentation, the presentation can identifyaccess characteristics about available access rights. The presentationcan include, for example, a chart that identifies available accessrights for an event and corresponding fees. Publisher engine 508 candistribute the presentation via, for example, a website, app page, emailand/or message. The presentation can be further configured to enable auser to request assignments of one or more access rights.

In some instances, an intermediate system coordination engine 510 canfacilitate transmission of information about resource availability(e.g., resource specifications and characteristics of resource-accessrights) to one or more intermediate systems (e.g., by generating one ormore messages that include such information and/or facilitatingpublishing such information via a website or app page). Each of the oneor more intermediate systems can publish information about the resourceand accept requests for resource access. In some instances, intermediatesystem coordination engine 510 identifies different access rights asbeing available to individual intermediate systems to coordinateassignment. For example, access rights for seats in Section 1 may beprovided for a first intermediate system to assign, and access rightsfor seats in Section 2 may be provided to a second intermediate systemto assign.

In some instances, overlapping access rights are made available tomultiple intermediate systems to coordinate assignments. For example,some or all of a first set of resource rights (e.g., corresponding to asection) may be provided to first and second intermediate systems. Insuch instances, intermediate system coordination engine 510 can respondto a communication from a first intermediate system indicating that arequest has been received (e.g., and processed) for an access right inthe set) by sending a notification to one or more other intermediatesystems that indicates that the access right is to be at leasttemporarily (or entirely) made unavailable.

Intermediate system coordination engine 510 can monitor communicationchannels with intermediate systems to track the health and security ofthe channel. For example, a healthy connection can be inferred whenscheduled signals are consistently received. Further, intermediatesystem coordination engine 510 can track configurations of intermediatesystems (e.g., via communications generated at the intermediate systemsvia a software agent that identifies such configurations) so as toinfluence code generation, communication format, and/or provisions oraccess rights.

Resource access coordinator module 416 may use tokens (generated by atoken engine 511) to convey information pertaining to a resource. Atoken may include, for example, a header, payload and signature. Theheader may identify a type or format pertaining to the payload. In someinstances, the header includes a key and/or an identifier of a techniquefor transforming the payload (e.g., a hashing algorithm or decryptiontechnique), such as one using a token-included key and/or a keypreviously provided to or provided by another system. The payload mayinclude one or more claims, each of which may include a claim name and aclaim value. Token engine 511 may use a transformation technique (e.g.,an encryption technique) to transform data elements in the token (e.g.,a header, payload, claims and/or signature) into a transformed versionthereof. The transformation technique may use a public key and/or aprivate key, such as a key provided to or provided by another system towhich the token is being transmitted.

In some instances, token engine 511 may generate a token thatcorresponds to one or more access rights. A token can include, forexample, data elements (e.g., claim values) that correspond to anidentifier of one, more or each of the following: a resource, acharacteristic (e.g., location and/or price) of particular access right(or plurality thereof), an access right, and an intermediate system. Inone instance, a token includes a data element that includes a storageaddress. The storage address may identify a location, within a datastore, that reflects information pertaining to a resource and/or accessright, such as whether a status of an access right indicates that it hasbeen assigned.

In some instances, a token can be used to convey information, such asinformation that identifies one or more access rights (e.g., that arecurrently available for a resource). In some instances, a token may beindicative of a preliminary authority, a general authority, atime-limited authority and/or a conditioned authority to assign anaccess right. For example, in one instance, transmission of a tokenassociated with an access right to a particular system may indicate thatthe system has an exclusive right to claim (e.g., and/or coordinateassignment of) the access right until an expiration time associated with(e.g., identified in) the token. As another example, transmission of thetoken may indicate that the system can coordinate an assignment of theassociated access right, which will be effected so long as it is thefirst system to convey coordination of an assignment of the associatedaccess right to a central system.

Tokens may be transmitted to intermediate systems upon authenticatingthe intermediate systems. For example, an intermediate system may beinitially authenticated (e.g., by an authentication engine 512) based onan evaluation of login credentials, an IP address, and/or a deviceidentifier. Such authentication may occur in response to receiving arequest communication from the intermediate system that identifies aresource and/or prior to (or separate from) any such request.

Upon authenticating the intermediate system, a token associated with theresource (e.g., and, in some instances, one or more access rights) maybe transmitted to the intermediate system. Any subsequent communicationfrom the intermediate system that requests assignment of an access rightfor the resource may include the token, which may have an effect ofindicating that an authentication corresponding to a proposed assignmentwas already performed and/or may identify details pertinent to theassignment (e.g., as the token can be indicative of a particularresource).

A token may, or may not, be specific to a given intermediate system. Forexample, a single token corresponding to a given resource (e.g., and, insome instances, one or more access rights) may be transmitted tomultiple intermediate systems. A particular intermediate system may thencommunicate with a user device so as to indicate that an access rightfor the resource is available, and the user device may send acommunication requesting assignment of the access right. In variousinstances (e.g., depending on a type of token transmitted to anintermediate system and/or to how many intermediate systems a tokencorresponding to a resource or access right was transmitted), it may ormay not be indicated that a single intermediate system has control ofcoordinating an assignment to an access right for a resource. Forexample, exclusive assignment control may be provided as a result of anintermediate system having purchased the access right and/or committedto purchasing the access right if it is not assigned to a user.

When such control is not exerted, intermediate system may send acommunication that includes the token (e.g., so as to identify aresource and/or access right and/or to be indicative of a previousauthentication) back to an access management system to confirm that anaccess right has not yet been assigned and/or request assignment. Insome instances, the communication may identify a user associated withthe user device and/or user device. When such control is exerted, invarious instances, intermediate system may (but need not) still send acommunication to an access management system that includes the tokenthat indicates that an access right is being assigned and/or thatinclude assignment data (e.g., an identifier of a user and/or userdevice).

Thus, either via a presentation facilitated by publisher engine 508(e.g., via a web site or app page) or via communication with anintermediate system, a request for assignment of an access right can bereceived. A request management engine 513 can process the request.Processing the request can include determining whether all otherrequired information has been received, such as user-identifyinginformation (e.g., name), access-right identifying information (e.g.,identifying a resource and/or resource-access characteristic) usercontact information (e.g., address, phone number, and/or email address),and/or user device information (e.g., type of device, device identifier,and/or IP address).

When all required information has not been received, request managementengine 513 can facilitate collection of the information (e.g., via awebpage, app page or communication to an intermediate system). Requestmanagement engine 513 can also or alternatively collect paymentinformation, determine that payment information has been received,obtain authorization of payment, determine that payment has beenauthorized (e.g., via an intermediate system), collect payment, and/ordetermine that payment has been collected. For example, publisher engine508 may receive a credit card number and expiration date via a webpage,and request management engine 513 can request authorization for anamount of the requested access rights. In some instances, paymentassessments are performed subsequent to at least temporary assignmentsof access rights. In some instances, request management engine 513retrieves data from a user account. For example, publisher engine 508may indicate that a request for an access right has been received whilea user was logged into a particular account. Request management engine513 may then retrieve, for example, contact information, deviceinformation, preferences and/or payment information associated with theaccount from account data store 424

When a request is received from an intermediate system—in variousinstances—information collected and assessed may correspond to an entityassociated with the intermediate system or a user associated with a userdevice with which the intermediate system was in contact. Similarly, ifa request is received from a user device but was made in response to aninteraction between the user device and an intermediate system,information collected and accessed may correspond to an entityassociated with the intermediate system. For example, a requestcommunication may include a token uniquely associated with a particularintermediate system. Request management engine 513 may then retrieveaccount information corresponding to the particular intermediate system.If an access right is assigned, it may be assigned to the intermediatesystem (which may assign it to a user) or to a user identified by theintermediate system.

In some instances, request management engine 513 prioritizes requests,such as requests for overlapping, similar or same access rights (e.g.,requests for access rights associated with a same section) receivedwithin a defined time period. The prioritization can be based on, forexample, times at which requests were received (e.g., prioritizingearlier requests), a request parameter (e.g., prioritizing requests fora higher or lower number of access rights above others), whetherrequests were received via an intermediate system (e.g., prioritizingsuch requests lower than others), intermediate systems associated withrequests (e.g., based on rankings of the systems), whether requests wereassociated with users having established accounts, and/or whetherrequests were associated with inputs indicative of a bot initiating therequest (e.g., shorter inter-click intervals, failed CAPTCHA tests,purchase history departing from a human profile).

Upon determining that required information has been received andrequest-processing conditions have been met, request management engine513 can forward appropriate request information to a resource schedulingengine 514. For a request, resource scheduling engine 514 can queryresource status data store 428 to identify access rights matchingparameters of the request.

In some instances, the request has an access-right specificity matchinga specificity at which access rights are assigned. In some instances,the request is less specific, and resource scheduling engine 514 canthen facilitate an identification of particular rights to assign. Forexample, request management engine 513 can facilitate a communicationexchange by which access right characteristics matching the request areidentified, and a user is allowed to select particular rights. Asanother example, request management engine 513 can itself select fromamongst matching access rights based on a defined criterion (e.g., bestsummed or averaged access-right ranking, pseudo-random selection, or aselection technique identified based on user input).

Upon identifying appropriately specific access rights, resourcescheduling engine 514 can update resource status data store 428 so as toplace the access right(s) on hold (e.g., while obtaining paymentauthorization and/or user confirmation) and/or to change a status of theaccess right(s) to indicate that they have been assigned (e.g.,immediately, upon receiving payment authorization or upon receiving userconfirmation). Such assignment indication may associate informationabout the user (e.g., user name, device information, phone number and/oremail address) and/or assignment process (e.g., identifier of anyintermediate system and/or assignment date and time) with an identifierof the access right(s). Resource scheduling engine 514 may further senda communication to one or more intermediate systems (e.g., notassociated with a request being processed) to indicate a change in thestatus of the access right and/or that a previously provided tokenassociated with the access right has expired.

For individual assigned access rights, an encoding engine 516 cangenerate an access-enabling code (or “access code”). The access-enablingcode can include, for example, an alphanumeric string, a text string, anumber, a graphic, a barcode (e.g., a 1-dimensional or 2-dimensionalbarcode), a static code, a dynamic code (e.g., with a feature dependingon a current time, current location or communication) and/or a techniquefor generating the code (e.g., whereby part of the code may be staticand part of the code may be determined using the technique). The codemay be unique across all access rights, all access rights for a givenresource, all access rights associated with a given location, all accessrights associated with a given time period, all resources and/or allusers. In some instances, at least part of the code is determined basedon or is thereafter associated with an identifier of a user, user deviceinformation, a resource specification and/or an access rightcharacteristic.

In various embodiments, the code may be generated prior to allocatingaccess rights (e.g., such that each of some or all allocated accessrights are associated with an access-enabling code), prior to or whileassigning one or more access right(s) responsive to a request (e.g.,such that each of some or all assigned access rights are associated withan access-enabling code), at a prescribed time, and/or when the deviceis at a defined location and/or in response to user input. The code maybe stored at or availed to a user device. In various instances, at theuser device, an access-enabling code may be provided in a manner suchthat it is visibly available for user inspection or concealed from auser. For example, a ticket document with a barcode may be transmittedto a user device, or an app on the user device can transmit a requestwith a device identifier for a dynamic code.

Encoding engine 516 can store the access-enabling codes inaccess-enabling code data store 430. Encoding engine 516 can also oralternatively store an indication in account data store 424 that theaccess right(s) have been assigned to the user. It will again beappreciated that data stores 424, 426, 428, and 430 can be relationaland/or linked, such that, for example, an identification of anassignment can be used to identify one or more access rights, associatedaccess-enabling code(s) and/or resource specifications.

Resource scheduling engine 514 can facilitate one or more transmissionsof data pertaining to one or more assigned access rights to a device ofa user associated with the assignment and/or to an intermediate systemfacilitating the assignment and/or having transmitted a correspondingassignment request. The data can include an indication that accessrights have been assigned and/or details as to which rights have beenassigned. The data can also or alternatively include access-enablingcodes associated with assigned access rights.

While FIG. 5 depicts components of resource access coordinator module516 that may be present on an access management system 120, it will beappreciated that similar or complementary engines may be present onother systems. For example, a communication engine on a user device canbe configured to display presentations identifying access rightavailability, and a request management engine on a user device can beconfigured to translate inputs into access-right requests to send to anintermediate system or access management system.

Returning to FIG. 4 , code verification module 418 (e.g., at a userdevice or client device) can analyze data to determine whether anaccess-enabling code is generally valid and/or valid for a particularcircumstance. The access-enabling code can include one that is receivedat or detected by device 400. The analysis can include, for example,determining whether all or part of the access-enabling code matches onestored in access-enabling code data store 430 or part thereof, whetherthe access-enabling code has previously been applied, whether all orpart of the access-enabling code is consistent with itself or otherinformation (e.g., one or more particular resource specifications, acurrent time and/or a detected location) as determined based on aconsistency analysis and/or whether all or part of the access-enablingcode has an acceptable format.

For example, access-enabling code data store 430 can be organized in amanner such that access-enabling codes for a particular resource, date,resource group, client, etc. can be queried to determine whether anysuch access-enabling codes correspond to (e.g. match) one beingevaluated, which may indicate that the code is verified. Additionalinformation associated with the code may also or alternatively beevaluated. For example, the additional information can indicate whetherthe code is currently valid or expired (e.g., due to a previous use ofthe code).

As another example, a portion of an access-enabling code can include anidentifier of a user device or user account, and code verificationmodule 418 can determine whether the code-identified device or accountmatches that detected as part of the evaluation. To illustrate, device400 can be a client device that electronically receives a communicationwith an access-enabling code from a user device. The communication canfurther include a device identifier that identifies, for example, thatthe user device is a particular type of smartphone. Code verificationmodule 418 can then determine whether device-identifying information inthe code is consistent with the identified type of smartphone.

As yet another example, code verification module 418 can identify a codeformat rule that specifies a format that valid codes are to have. Toillustrate, the code format rule may identify a number of elements thatare to be included in the code or a pattern that is to be present in thecode. Code verification module 418 can then determine that a code is notvalid if it does not conform to the format.

Verification of an access-enabling code can indicate that access to aresource is to be granted. Conversely, determining that a code is notverified can indicate that access to a resource is to be limited orprevented. In some instances, a presentation is generated (e.g., andpresented) that indicates whether access is to be granted and/or aresult of a verification analysis. In some instances, access grantingand/or limiting is automatically affected. For example, upon a codeverification, a user device and/or user may be automatically permittedto access a particular resource. Accessing a resource may include, forexample, using a computational resource, possessing an item, receiving aservice, entering a geographical area, and/or attending an event (e.g.,generally or at a particular location).

Verification of an access-enabling code can further trigger amodification to access-enabling code data store 430. For example, a codethat has been verified can be removed from the data store or associatedwith a new status. This modification may limit attempts to use a samecode multiple times for resource access.

A combination of modules 414, 416, 418 comprise a secure addressableendpoint agent 420 that acts as an adapter and enables cross-deviceinterfacing in a secure and reliable fashion so as to facilitateallocation of access-enabling codes and coordinate resource access.Secure addressable endpoint agent 420 can further generate a healthsignal that is transmitted to another device for monitoring of a statusof a communication channel. The health signal is optionally a shortmessage of a few bytes or many bytes in length that may be transmittedon a frequent basis (e.g., every few milliseconds or seconds). Acommunications manager 406 on the receiving device can then monitors thehealth signal provided by the agent to ensure that the communicationlink between the host server and device 400 is still operational.

In some instances, device 400 can include (or can be in communicationwith) a physical access control 432. Physical access control 432 caninclude a gating component that can be configured to provide a physicalbarrier towards accessing a resource. For example, physical accesscontrol 432 can include a turnstile or a packaging lock.

Physical access control 432 can be configured such that it can switchbetween two modes, which differ in terms of a degree to which useraccess to a resource is permitted. For example, a turnstile may have alocked mode that prevents movement of an arm of the turnstile and anunlocked mode that allows the arm to be rotated. In some instances, adefault mode is the mode that is more limiting in terms of access.

Physical access control 432 can switch its mode in response to receivingparticular results from code verification module 418. For example, uponreceiving an indication that a code has been verified, physical accesscontrol 432 can switch from a locked mode to an unlocked mode. It mayremain in the changed state for a defined period of time or until anaction or event is detected (e.g., rotation of an arm).

Device 400 can also include one or more environmental sensors 434.Measurements from the sensor can processed by one or more applicationmodules. Environmental sensor(s) 434 can include a global positioningsystem (GPS) receiver 435 that can receive signals from one or more GPSsatellites. A GPS chipset can use the signals to estimate a location ofdevice 400 (e.g., a longitude and latitude of device 400). The estimatedlocation can be used to identify a particular resource (e.g., one beingoffered at or near the location at a current or near-term time). Theidentification of the particular resource can be used, for example, toidentify a corresponding (e.g., user-associated) access-enabling code orto evaluate an access-enabling code (e.g., to determine whether itcorresponds to a resource associated with the location).

The estimated location can further or alternatively be used to determinewhen to perform a particular function. For example, at a user device,detecting that the device is in or has entered a particular geographicalregion (e.g., is within a threshold distance from a geofence perimeteror entrance gate) can cause the device to retrieve or request anaccess-enabling code, conduct a verification analysis of the code and/ortransmit the code to a client device.

It will be appreciated that environmental sensor(s) 434 can include oneor more additional or alternative sensors aside from GPS receiver 435.For example, a location of device 400 can be estimated based on signalsreceived by another receive from different sources (e.g., base stations,client point devices or Wi Fi access points). As another example, anaccelerometer and/or gyroscope can be provided. Data from these sensorscan be used to infer when a user is attempting to present anaccess-enabling code for evaluation.

It will also be appreciated that the components and/or engines depictedin figures herein are illustrative, and a device need not include eachdepicted component and/or engine and/or can include one or moreadditional components and/or engines. For example, a device can alsoinclude a user interface, which may include a touch sensor, keyboard,display, camera and/or speakers. As another example, a device caninclude a power component, which can distribute power to components ofthe device. The power component can include a battery and/or aconnection component for connecting to a power source. As yet anotherexample, a module in the application layer can include an operatingsystem. As still another example, an application-layer control processormodule can provide message processing for messages received from anotherdevice. The message processing can include classifying the message androuting it to the appropriate module. To illustrate, the message can beclassified as a request for resource access or for an access-enablingcode, an update message or an indication that a code has been redeemedor verified. The message processing module can further convert a messageor command into a format that can interoperate with a target module.

It will further be appreciated that the components, modules and/oragents could be implemented in one or more instances of software. Thefunctionalities described herein need not be implemented in separatemodules, for example, one or more functions can be implemented in onesoftware instance and/or one software/hardware combination. Othercombinations are similarly be contemplated.

Further yet, it will be appreciated that a storage medium (e.g., usingmagnetic storage media, flash memory, other semiconductor memory (e.g.,DRAM, SRAM), or any other non-transitory storage medium, or acombination of media, and can include volatile and/or non-volatilemedia) can be used to store program code for each of one or more of thecomponents, modules and/or engines depicted in FIGS. 4 and 5 and/or tostore any or all data stores depicted in FIG. 4 or described withreference to FIGS. 4 and/or 5 . Any device or system disclosed hereincan include a processing subsystem for executing the code. Theprocessing system can be implemented as one or more integrated circuits,e.g., one or more single-core or multi-core microprocessors ormicrocontrollers, examples of which are known in the art.

FIG. 6 illustrates a flowchart of an embodiment of a process 600 forassigning access rights for resources. Process 600 can be performed byan access management system, such as access management system 120.Process 600 begins at block 605 where resource specification engine 502identifies one or more specifications for a resource. The specificationscan include, for example, a time at which the resource is to beavailable, a location of the resource, a capacity of the resourcesand/or one or more entities (e.g., performing entities) associated withthe resource.

At block 610, resource-access allocation engine 504 allocates a set ofaccess rights for the resource. In some instances, each of at least someof the access rights corresponds to a different access parameter, suchas a different location (e.g., seat) assignment. Upon allocation, eachof some or all of the access rights may have a status as available. Asubset of the set of access rights can be immediately (or at a definedtime) assigned or reserved according to a base assignment or reservationrule (e.g., assigning particular access rights to particular entities,who may be involved in or related to provision of the resource and/orwho have requested or been assigned a set of related access rights.

At block 615, communication engine 506 transmits the resourcespecifications and data about the access rights. The transmission canoccur in one or more transmissions. The transmission can be to, forexample, one or more user devices and/or intermediate systems. In someinstances, a notification including the specifications and access-rightdata is transmitted, and in some instances, a notification can begenerated at a receiving device based on the specifications andaccess-right data. The notification can include, for example, a websitethat identifies a resource (via, at least in part, its specifications)and indicates that access rights for the resource are available forassignment. The notification can include an option to request assignmentof one or more access rights.

At block 620, request management engine 513 receives a request for oneor more access rights to be assigned to a user. The request can, forexample, identify particular access rights and/or access parameters. Therequest can include or be accompanied by other information, such asidentifying information. In some instances, the access management systemcan use at least some of such information to determine whether a fee forthe access rights has been authorized. In some instances, the request isreceived via an intermediate system that has already handled suchauthorization.

At block 625, resource scheduling engine 514 assigns the requested oneor more access rights to the user. The assignment can be conditioned onreceipt of all required information, confirmation that the accessright(s) have remained available for assignment, determining using datacorresponding to the request that a bot-detection condition is notsatisfied, fee provision and/or other defined conditions. Assignment ofthe access right(s) can include associating an identifier of each of theone or more rights with an identifier of a user and/or assignment and/orchanging a status of the access right(s) to assigned. Assignment of theaccess right(s) can result in impeding or preventing other users fromrequesting the access right(s), being assigned the access right(s)and/or being notified that the access right(s) are available forassignment. Assignment of the access right(s) can, in some instances,trigger transmission of one or more communications to, for example, oneor more intermediate systems identifying the access right(s) andindicating that they have been assigned and/or with an instruction tocease offering the access rights.

At block 630, encoding engine 516 generates an access-enabling code foreach of the one or more access rights. The code can be generated, forexample, as part of the assignment, as part of the allocation orsubsequent to the assignment (e.g., upon detecting that a user isrequesting access to the resource). Generating an access-enabling codecan include applying a code-generation technique, such on one thatgenerates a code based on a characteristic of a user, user device,current time, access right, resource, intermediate system or othervariable. The access-enabling code can include a static code that willnot change after it has been initially generated or a dynamic code thatchanges in time (e.g., such that block 630 can be repeated at varioustime points).

At block 635, communication engine 506 transmits a confirmation of theassignment and the access-enabling code(s) in one or more transmissions.The transmission(s) may be sent to one or more devices, such as a userdevice having initiated the request from block 620, a remote server oran intermediate system having relayed the request from block 620.

Referring to FIG. 7A, an embodiment of a site system 180 is shown inrelation to mobile devices 724-n, Network Attached Storage (NAS) 750,site network 716 and the Internet 728. In some embodiments, forattendees of a live event or concert, site network 716 and site system180 provide content, services and/or interactive engagement using mobiledevices 724. Connections to site system 180 and site network 716 can beestablished by mobile devices 724 connecting to access points 720.Mobile devices 724 can be a type of end user device 110 that isportable, e.g., smartphones, mobile phones, tablets, and/or othersimilar devices.

Site network 716 can have access to content (information aboutattendees, videos, pictures, music, trivia information, etc.) held byNAS 750. Additionally, as described herein, content can be gathered fromattendees both before and during the event. By connecting to sitenetwork 716, mobile device 724 can send content for use by site system180 or display content received from NAS 750.

Referring to FIG. 7B, another embodiment of a site system 180 is shownin relation to mobile devices 724-n, Network Attached Storage (NAS) 750,site network 716 and the Internet 728, in an embodiment. FIG. 7Badditionally includes phone switch 740. In some embodiments, phoneswitch 740 can be a private cellular base station configured to spoofthe operation of conventionally operated base stations. Using phoneswitch 740 at an event site allows site system 180 to provide additionaltypes of interactions with mobile devices 724. For example, without anysetup or configuration to accept communications from site controller712, phone switch 740 can cause connected mobile devices 724 to ringand, when answered, have an audio or video call be established. Whenused with other embodiments described herein, phone switch 740 canprovide additional interactions. For example, some embodiments describedherein use different capabilities of mobile devices 724 to cause masssounds and/or establish communications with two or more people. Bycausing phones to ring and by establishing cellular calls, phone switchcan provide additional capabilities to these approaches.

FIG. 8 shows a block diagram of user device 110 according to anembodiment. User device 110 includes a handheld controller 810 that canbe sized and shaped so as enable the controller and user device 110 in ahand. Handheld controller 810 can include one or more user-deviceprocessors that can be configured to perform actions as describedherein. In some instances, such actions can include retrieving andimplementing a rule, retrieving an access-enabling code, generating acommunication (e.g., including an access-enabling code) to betransmitted to another device (e.g., a nearby client-associated device,a remote device, a central server, a web server, etc.), processing areceived communication (e.g., to perform an action in accordance with aninstruction in the communication, to generate a presentation based ondata in the communication, or to generate a response communication thatincludes data requested in the received communication) and so on.

Handheld controller 810 can communicate with a storage controller 820 soas to facilitate local storage and/or retrieval of data. It will beappreciated that handheld controller 810 can further facilitate storageand/or retrieval of data at a remote source via generation ofcommunications including the data (e.g., with a storage instruction)and/or requesting particular data.

Storage controller 820 can be configured to write and/or read data fromone or more data stores, such as an application storage 822 and/or auser storage 824. The one or more data stores can include, for example,a random access memory (RAM), dynamic random access memory (DRAM),read-only memory (ROM), flash-ROM, cache, storage chip, and/or removablememory. Application storage 822 can include various types of applicationdata for each of one or more applications loaded (e.g., downloaded orpre-installed) onto user device 110. For example, application data caninclude application code, settings, profile data, databases, sessiondata, history, cookies and/or cache data. User storage 824 can include,for example, files, documents, images, videos, voice recordings and/oraudio. It will be appreciated that user device 110 can also includeother types of storage and/or stored data, such as code, files and datafor an operating system configured for execution on user device 110.

Handheld controller 810 can also receive and process (e.g., inaccordance with code or instructions generated in correspondence to aparticular application) data from one or more sensors and/or detectionengines. The one or more sensors and/or detection engines can beconfigured to, for example, detect a presence, intensity and/or identifyof (for example) another device (e.g., a nearby device or devicedetectable over a particular type of network, such as a Bluetooth,Bluetooth Low-Energy or Near-Field Communication network); anenvironmental, external stimulus (e.g., temperature, water, light,motion or humidity); an internal stimulus (e.g., temperature); a deviceperformance (e.g., processor or memory usage); and/or a networkconnection (e.g., to indicate whether a particular type of connection isavailable, a network strength and/or a network reliability).

FIG. 8 shows several exemplary sensors and detection engines, includinga peer monitor 830, accelerometer 832, gyroscope 834, light sensor 836and location engine 838. Each sensor and/or detection engine can beconfigured to collect a measurement or make a determination, forexample, at routine intervals or times and/or upon receiving acorresponding request (e.g., from a processor executing an applicationcode).

Peer monitor 830 can monitor communications, networks, radio signals,short-range signals, etc., which can be received by a receiver of userdevice 110) Peer monitor 830 can, for example, detect a short-rangecommunication from another device and/or use a network multicast orbroadcast to request identification of nearby devices. Upon or whiledetecting another device, peer monitor 830 can determine an identifier,device type, associated user, network capabilities, operating systemand/or authorization associated with the device. Peer monitor 530 canmaintain and update a data structure to store a location, identifierand/or characteristic of each of one or more nearby user devices.

Accelerometer 832 can be configured to detect a proper acceleration ofuser device 110. The acceleration may include multiple componentsassociated with various axes and/or a total acceleration. Gyroscope 834can be configured to detect one or more orientations (e.g., viadetection of angular velocity) of user device 110. Gyroscope 834 caninclude, for example, one or more spinning wheels or discs, single- ormulti-axis (e.g., three-axis) MEMS-based gyroscopes.

Light sensor 836 can include, for example, a photosensor, such asphotodiode, active-pixel sensor, LED, photoresistor, or other componentconfigured to detect a presence, intensity and/or type of light. In someinstances, the one or more sensors and detection engines can include amotion detector, which can be configured to detect motion. Such motiondetection can include processing data from one or more light sensors(e.g., and performing a temporal and/or differential analysis).

Location engine 838 can be configured to detect (e.g., estimate) alocation of user device 110. For example, location engine 838 can beconfigured to process signals (e.g., a wireless signal, GPS satellitesignal, cell-tower signal, iBeacon, or base-station signal) received atone or more receivers (e.g., a wireless-signal receiver and/or GPSreceiver) from a source (e.g., a GPS satellite, cellular tower or basestation, or WiFi access point) at a defined or identifiable location. Insome instances, location engine 838 can process signals from multiplesources and can estimate a location of user device 110 using atriangulation technique. In some instances, location engine 838 canprocess a single signal and estimate its location as being the same as alocation of a source of the signal.

User device 110 can include a flash 842 and flash controller 846. Flash842 can include a light source, such as (for example), an LED,electronic flash or high-speed flash. Flash controller 846 can beconfigured to control when flash 842 emits light. In some instances, thedetermination includes identifying an ambient light level (e.g., viadata received from light sensor 836) and determining that flash 842 isto emit light in response to a picture- or movie-initiating input whenthe light level is below a defined threshold (e.g., when a setting is inan auto-flash mode). In some additional or alternative instances, thedetermination includes determining that flash 846 is, or is not, to emitlight in accordance with a flash on/off setting. When it is determinedthat flash 846 is to emit light, flash controller 846 can be configuredto control a timing of the light so as to coincide, for example, with atime (or right before) at which a picture or video is taken.

User device 110 can also include an LED 840 and LED controller 844. LEDcontroller 844 can be configured to control when LED 840 emits light.The light emission may be indicative of an event, such as whether amessage has been received, a request has been processed, an initialaccess time has passed, etc.

Flash controller 846 can control whether flash 846 emits light viacontrolling a circuit so as to complete a circuit between a power sourceand flash 846 when flash 842 is to emit light. In some instances, flashcontroller 846 is wired to a shutter mechanism so as to synchronizelight emission and collection of image or video data.

User device 110 can be configured to transmit and/or receive signalsfrom other devices or systems (e.g., over one or more networks, such asnetwork(s) 170). These signals can include wireless signals, andaccordingly user device 110 can include one or more wireless modules 850configured to appropriately facilitate transmission or receipt ofwireless signals of a particular type. Wireless modules 850 can includea Wi-Fi module 852, Bluetooth module 854, near-field communication (NFC)module 856 and/or cellular module 856. Each module can, for example,generate a signal (e.g., which may include transforming a signalgenerated by another component of user device 110 to conform to aparticular protocol and/or to process a signal (e.g., which may includetransforming a signal received from another device to conform with aprotocol used by another component of user device 110).

Wi-Fi module 854 can be configured to generate and/or process radiosignals with a frequency between 2.4 gigahertz and 5 gigahertz. Wi-Fimodule 854 can include a wireless network interface card that includescircuitry to facilitate communicating using a particular standard (e.g.,physical and/or link layer standard).

Bluetooth module 854 can be configured to generate and/or process radiosignals with a frequency between 2.4 gigahertz and 2.485 gigahertz. Insome instances, bluetooth module 854 can be configured to generateand/or process Bluetooth low-energy (BLE or BTLE) signals with afrequency between 2.4 gigahertz and 2.485 gigahertz.

NFC module 856 can be configured to generate and/or process radiosignals with a frequency of 13.56 megahertz. NFC module 856 can includean inductor and/or can interact with one or more loop antenna.

Cellular module 858 can be configured to generate and/or processcellular signals at ultra-high frequencies (e.g., between 698 and 2690megahertz). For example, cellular module 858 can be configured togenerate uplink signals and/or to process received downlink signals.

The signals generated by wireless modules 850 can be transmitted to oneor more other devices (or broadcast) by one or more antennas 859. Thesignals processed by wireless modules 850 can include those received byone or more antennas 859. One or more antennas 859 can include, forexample, a monopole antenna, helical antenna, intenna, Planar Inverted-FAntenna (PIFA), modified PIFA, and/or one or more loop antennae.

User device 110 can include various input and output components. Anoutput component can be configured to present output. For example, aspeaker 862 can be configured to present an audio output by convertingan electrical signal into an audio signal. An audio engine 864 caneffect particular audio characteristics, such as a volume,event-to-audio-signal mapping and/or whether an audio signal is to beavoided due to a silencing mode (e.g., a vibrate or do-not-disturb modeset at the device).

Further, a display 866 can be configured to present a visual output byconverting an electrical signal into a light signal. Display 866 mayinclude multiple pixels, each of which may be individually controllable,such that an intensity and/or color of each pixel can be independentlycontrolled. Display 866 can include, for example, an LED- or LCD-baseddisplay.

A graphics engine 868 can determine a mapping of electronic image datato pixel variables on a screen of user device 110. It can further adjustlighting, texture and color characteristics in accordance with, forexample, user settings.

In some instances, display 866 is a touchscreen display (e.g., aresistive or capacitive touchscreen) and is thus both an input and anoutput component. A screen controller 870 can be configured to detectwhether, where and/or how (e.g., a force of) a user touched display 866.The determination may be made based on an analysis of capacitive orresistive data.

An input component can be configured to receive input from a user thatcan be translated into data. For example, as illustrated in FIG. 8 ,user device 110 can include a microphone 872 that can capture audio dataand transform the audio signals into electrical signals. An audiocapture module 874 can determine, for example, when an audio signal isto be collected and/or any filter, equalization, noise gate, compressionand/or clipper that is to be applied to the signal.

User device 110 can further include one or more cameras 876, 880, eachof which can be configured to capture visual data (e.g., at a given timeor across an extended time period) and convert the visual data intoelectrical data (e.g., electronic image or video data). In someinstances, user device 110 includes multiple cameras, at least two ofwhich are directed in different and/or substantially oppositedirections. For example, user device 110 can include a rear-facingcamera 876 and a front-facing camera 880.

A camera capture module 878 can control, for example, when a visualstimulus is to be collected (e.g., by controlling a shutter), a durationfor which a visual stimulus is to be collected (e.g., a time that ashutter is to remain open for a picture taking, which may depend on asetting or ambient light levels; and/or a time that a shutter is toremain open for a video taking, which may depend on inputs), a zoom, afocus setting, and so on. When user device 110 includes multiplecameras, camera capture module 878 may further determine which camera(s)is to collect image data (e.g., based on a setting).

FIG. 9 illustrates sample components of an embodiment of site system180, including connections to NAS 750 and access management system 185.Embodiments of site controller 712 use network manager 920 to connectvia access points 720 (using e.g., WiFi 952, Bluetooth 953, NFC 956,Ethernet 958, and/or other network connections) to other networkcomponents, such as site network 716 and mobile devices 724. In someembodiments, site system 280 uses site controller 712 to control aspectsof an event venue. A broad variety of venue features can be controlledby different embodiments, including: permanent lights (e.g., withlighting controller 922), stage lights (e.g., with presentmentcontroller 924), stage display screens (e.g., with stage display(s)controller 912), permanent display screens (e.g., with permanentdisplay(s) controller 914), and the venue sound system (e.g., with thesound system controller 916).

A more detailed view of NAS 750 is shown, including NAS controller 930coupled to user video storage 932, captured video storage 934,preference storage 936, and 3D model 938. Captured video storage 934 canreceive, store and provide user videos received from mobile devices 724.In some embodiments, site controller 712 triggers the automatic captureof images, audio and video from mobile devices 724, such triggeringbeing synchronized to activities in an event. Images captured by thisand similar embodiments can be stored on both the capturing mobiledevice 724 and user video storage 932. In an embodiment, site controller712 can coordinate the transfer of information from mobile devices toNAS 750 (e.g., captured media) with activities taking place during theevent. When interacting with mobile devices 724, some embodiments ofsite controller 712 can provide end user interfaces 926 to enabledifferent types of interaction. For example, as a part of engagementactivities, site controller may offer quizzes and other content to thedevices. Additionally, with respect to location determinations discussedherein, site controller can supplement determined estimates withvoluntarily provided information using end user interfaces 926, storedin a storage that is not shown.

In some embodiments, to guide the performance of different activities,site controller 712 and/or other components may use executable code 938tangibly stored in code storage 939. In some embodiments, siteinformation storage 937 can provide information about the site, e.g.,events, seat maps, attendee information, geographic location ofdestinations (e.g., concessions, bathrooms, exits, etc.), as well as 3Dmodels of site features and structure.

In some embodiments, tokens are transmitted across systems, which caninhibit unauthorized access to and use of access codes. Use of tokensmay be particularly advantageous when communicating with one or moresecondary assignment management systems and/or conveying informationpertaining to access rights prior to assignments. FIGS. 10A-10Dillustrate examples of communication exchanges between systems involvingidentifications of tokens and access codes.

In FIG. 10A, a first communication is transmitted from a secondaryassignment management system 216 (e.g., which may correspond to anintermediate system) to a primary assignment system 214 (e.g., which maycorrespond to an access management system and may include one or morecomponents depicted or described herein, such as those depicted in FIG.4 and/or FIG. 5 ). The first communication includes or is indicative ofa request. In some instances, the first communication may include anidentifier of a resource, a characteristic for accessing the resource(e.g., a section), and/or an identifier associated with an entityassociated with the secondary assignment management system 216 (e.g., alogin name and/or password or metadata including an IP address and/ordevice identifier).

Primary assignment management system 214 may process the request todetermine whether to authenticate secondary assignment management system216 and/or an entity associated therewith. The authentication mayinclude, for example, determining whether a credential (e.g., a usernameand/or password, IP address, and/or device identifier) included in orotherwise associated with the request is valid and/or matches acredential in a local or remote data store.

Upon a authenticating secondary assignment management system 216 and/oran entity associated therewith, primary assignment system may generateor retrieve a token associated with a resource. The token can includeand/or can be an alphanumeric string, which may (but need not) be orconfigured to be transformed via a transformation technique (e.g., anencryption technique). In various instances, the token may be associatedwith a particular access right, a particular set of access rights, anresource-access characteristic (e.g., and, in some instances, any accessrights associated therewith), and/or a resource iteration (e.g.,corresponding to a time and/or location). For example, primaryassignment management system 214 may identify a set of access rightswith an unassigned status (e.g., by look-up at a local or remoteassignment data store 1010 a). One or more tokens may be generated tocorrespond to some or all of these access rights. In various instances,a given token is generated and/or stored so as to uniquely correspond toa particular secondary assignment management systems.

In one instance, primary assignment management system 214 identifies setof access rights for a resource and associates different portionsthereof with different secondary assignment management systems. A set oftokens transmitted to the secondary systems can then correspond todifferent secondary systems and to different access rights. In oneinstance, primary assignment management system 214 associatesoverlapping portions of the set with different secondary assignmentmanagement systems or associates the entire set with each secondaryassignment management systems. One or more tokens transmitted todifferent secondary assignment management systems may, in someinstances, still differ from each other (e.g., due to being associatedwith different secondary systems), or they may be the same (e.g., as aresult of corresponding to one or more same access rights and resource).

Therefore, in some instances, a set of tokens is generated and stored ata local or remote token data store 1005 a managed by and/or accessibleto primary assignment management system 214. Each token in the set oftokens may be different than the rest, and each token may have aparticular correspondence to one or more resources, access rights,resource-access characteristics, secondary assignment managementsystems, and so on.

A token may correspond to (for example) an indication that a system orentity provided with the token from primary assignment management system214 is entitled to assign a corresponding access right for a resource toa user. Such entitlement, in some instances, is conditioned, such as onethat indicates that an instruction from a token-associated system orentity to assign an access right to a user will be accepted so long asthe access right has not already been assigned to another user (e.g.,via a different secondary assignment management system or entity). Asanother example, the instruction may be accepted so long as payment fromthe token-associated system or entity or the user is collected orauthorized (e.g., via provision of payment information and/or retrievalof such from an account and/or a successful transaction communicationwith a payment management entity).

A token may additionally or alternatively correspond to (for example) anindication that a subsequent communication or communication session thatincludes the token need not be fully authenticated (or authenticated atall). A token, in some instances, may be time-limited. For example, atoken may include and/or represent an expiration date and/or time, afterwhich the token is no longer valid. As another example, a communicationsent to a secondary assignment management system that includes the tokenmay also include an expiration date and/or time.

Upon authentication of secondary assignment management system 216,primary assignment management system 214 transmits token data thatincludes a token to secondary assignment management system 216.Secondary assignment management system 216 may then store the token in atoken data store 1005 b managed by and/or accessible to secondaryassignment management system 214. It will be appreciated that, invarious instances, this authentication may be particularly tied to asingle token delivery or a general authentication. For example, asecondary assignment management system 216 may send an initial requestcommunication for all access rights corresponding to resources at agiven location. Primary assignment management system 214 may perform anauthentication and then send tokens for particular resources upondetecting new access-right allocations corresponding to the givenlocation.

Each token stored at token data store 1005 b may represent, identify orotherwise be associated with a given resource. Secondary assignmentmanagement system 216 may also manage and/or have access to a resourcespecification data store 1015. Such specifications may be collectedfrom, for example, primary assignment management system 214, othersystems, and/or web crawling. A resource specification may include text,graphics, or a video. A specification may identify, for example, one ormore performing entities, a location of the resource, and/or a locationassociated with one or more access rights relative to a performingentity.

Secondary assignment management system 216 can transmit resource data toone or more user devices. The resource data can include one or moreresource specifications and may be transmitted, for example, in responseto receiving an electronic query with one or more parameterscorresponding to the resource. The resource data may be provided via,for example, a webpage. In some instances, in addition to transmittingthe resource data, secondary assignment management system 216 transmitsdata corresponding to one or more access rights for the resource, suchas one or more access rights corresponding to a token and/or one or moreaccess rights detected by secondary assignment management system 216(e.g., via assignment data from an assignment data store 1010 b managedby and/or accessible to secondary assignment management system 216and/or via communicating with primary assignment management system 214)as having an available status.

A user device 210 may transmit an assignment request communication tosecondary assignment management system 216. The assignment request mayidentify and/or be indicative of a resource, particular access rightand/or resource-access characteristic. The assignment requestcommunication may be transmitted in response, for example, topresentation of some or all of the resource data. For example, a usermay use a webpage to submit a query. Secondary assignment managementsystem 216 may retrieve resource specifications pertaining to the queryand transmit corresponding resource data to user device 210 via thewebpage. A user may then select an access-right representation and/orrequest indication to initiate transmission of the assignment requestcommunication.

The assignment request communication (or a different correspondingcommunication) may include information pertaining to the user and/oruser device. Secondary assignment management system 216 may determinewhether all required information has been provided and whether local toand/or managed by secondary assignment management system 216 indicatesthat a status of a requested access right (or an access rightcorresponding to a resource and/or resource-access characteristicassociated with the assignment request communication) remainsunassigned.

Secondary assignment management system 216 can then retrieve a tokenfrom token data store 1005 b that corresponds to an access rightassociated with the request (e.g., identified in the request and/orhaving an resource-access characteristic identified in the request). Thetoken can be transmitted to one or more systems and/or devices. Forexample, secondary assignment management system 216 can transmit acommunication that includes the token back to primary assignmentmanagement system 214 to indicate that an access right corresponding tothe token is to be assigned to a particular user or has been assigned toa particular user (e.g., depending on which system has control ofissuing such assignments). In some instances, the communication mayinclude or may have an effect of being an instruction to change a statusof the access right in assignment data store 1010 a and/or to associatean identifier of the access right with an identifier of the particularuser in assignment data store 1010 a. Thus, the communication may (butneed not) include assignment data, which can identify a user, a userdevice and/or an access right.

Upon receiving the communication from secondary assignment system 216,primary assignment management system 214 may update token data store1005 a to indicate that the token and/or any other token associated witha same access right identified as being assigned is expired. Primaryassignment management system 214 may transmit an expirationcommunication to one or more other secondary assignment managementsystems (e.g., to which a same or different token associated with thesame access right was previously provided) to indicate that the tokenhas expired. Primary assignment management system 214 may further updateassignment data store to change a status of an access right to“assigned” and/or to associate it with an identifier of one or more of:second assignment management system 216, an identified user, user device210 and/or the token.

Secondary assignment management system 216 can further update assignmentdata store 1010 b to indicate that a particular access right isassigned, not available and/or assigned to a particular user. Secondaryassignment management system 216 may also update token data store 1005 bto remove the token and/or to indicate that it has expired or been used.

Secondary assignment management system 216 can also transmit the tokenback to user device 210 (e.g., via a website, app page, email or SMSmessage). The token can be transmitted along with an indication that acorresponding access right is being assigned. User device 210 can thenstore the token in a token data store 1005 c that is local to and/oraccessible to the device.

Subsequently, user device 210 may retrieve the token and transmit it toprimary assignment management system 214 so as to request an access codefor the corresponding access right. The token retrieval and/ortransmission may occur, for example, upon detecting a user inputcorresponding to a request for the access code, detecting a sitecontroller 712, detecting (e.g., via tracking GPS coordinates) that userdevice 210 is within a prescribed geographical area associated with theresource, detecting that a time threshold (e.g., that is a defined timebefore a resource-associated time) has elapsed and/or detecting arequest from a device or system (e.g., site controller 712) for anaccess code.

Depending on the embodiment, primary assignment management system 214may, or may not, verify that the token corresponds with a user and/oruser data identified in association with the token in assignment datastore 1010 a. Primary assignment management system 214 may then retrieveor generate an access code that corresponds to the token. The accesscode can include one previously stored at or store, subsequent toreal-time generation thereof, at an access code data store 1020 amanaged by and/or local to primary assignment management system 214. Theaccess code can include, for example, a one-, two-, three- orfour-dimensional code (e.g., one that changes in time).

User device 210 may store the access code at an access code data store1020 c local to and/or accessible to the user device. Immediately orsubsequently, user device 210 may also transmit the access code to asite controller 712. The transmission of the access code to sitecontroller 712 may occur (for example) in response to detecting the sitecontroller, in response to receiving a request from site controller 712for the access code and/or in response to detecting user inputcorresponding an instruction to transmit the access code. In someinstances, user device 210 may—in a same or differentcommunication—transmit additional information, such as an identifier ofuser device 210 and/or an identifier of an associated user.

Site controller 712 can communicate with primary assignment managementsystem 214 to verify that the access code is valid and is applicable toa given circumstance. Specifically, site controller 712 may transmit theaccess code to primary assignment management system 214 along with otherinformation, such as (for example) an identifier of user device 210, anidentifier of a user, an identifier of a resource, or a locationcharacteristic.

Primary assignment management system 214 may determine whether theaccess code is valid by, for example, identifying whether the codeexists in access code data store 1020 a, whether the code exists inaccess code data store 1020 a and is associated with one or more givenstatuses (e.g., assigned and unredeemed), and/or whether the codeconforms to a particular pattern. Primary assignment management system214 may further determine whether the access code corresponds withinformation in access code data store 1020 a that is consistent withother information transmitted by site controller 712, such as anidentifier of a user device, a resource, a user or a location. Upondetermining that the access code is valid (e.g., and applicable to agiven circumstance, as estimated based on an information consistencyanalysis), primary assignment management system 214 may change a statusof the access code in access code data store 1020 a to indicate that ithas been used, and transmit verification data back to site controller712 indicating that the access code is verified. If it is determinedthat the access code is not valid and/or not applicable to a givencircumstance, primary assignment management system 214 can transmitverification data back to site controller 712 indicating that the accesscode is not verified.

Site controller 712 can use a verification communication to (forexample) determine whether to unlock a gate of a resource and/or tocontrol a presentation. For example, an indication that an access codeis verified can cause a gate to unlock or a notification to be presentedthat an access code is verified.

In FIG. 10B, initial communications parallel those depicted in FIG. 10A.However, in this instance, secondary assignment management system 216does not transmit token data to user device 210. Rather, assignment datatransmitted from secondary assignment management system 216 to primaryassignment management system 214 that includes an identifier of userdevice 210 or an associated user.

Primary assignment management system 214 can then send access code datathat includes an access code that corresponds to the token. For example,the assignment data may identify user device 210, and the access codecan then be sent to user device 210. As another example, the assignmentdata may identify a user. User device 210 (which may be a same ordifferent user device from the one used to request an assignment) maythen detect association with a user and transmit a communication toprimary assignment management system 214 that identifies the user (e.g.,via a username and/or password, account identifier, etc.). As yetanother example, secondary assignment management system 216 may provideuser device 210 with a code (e.g., that is also provided to primaryassignment management system 214 or was provided by primary assignmentmanagement system 214). A communication from user device 210 (which maybe the same or different user device from one used to request anassignment) may then indicate that the user device corresponds to theuser.

The access code data can be transmitted to user device 210 (for example)upon receiving (e.g., immediately upon receiving) the assignment data,upon detecting that a time threshold defined based on aresource-associated time has passed, and/or upon receiving a request orother communication from user device 210. Subsequently, user device 210can transmit the access code to site controller 712, which cancommunicate with primary assignment management system 214 to determinewhether the code is verified, as in FIG. 10A.

In FIG. 10C, initial communications parallel those depicted in FIG. 10A.However, in this instance, secondary assignment management system 216provides user device 210 with an access code (e.g., as opposed toprimary assignment management system 214 providing such a code). Morespecifically, in response to receiving token data from secondaryassignment management system 216, primary assignment management system214 provides secondary assignment management system 216 with acorresponding access code. The access code may be provided, for example,immediately, at a defined delay, or upon detecting that a time thresholddefined based on a resource-associated time has passed.

Secondary assignment management system 216 may store the access code inan access code data store 1020 b that is local and/or accessible tosecondary assignment management system 216. Secondary assignmentmanagement system 216 can then transmit the access code to user device210. The access code can be transmitted to user device 210, for example,immediately, at a defined delay, or upon detecting that a time thresholddefined based on a resource-associated time has passed. Thus, in thiscontext, one or both of primary assignment management system 214 and/orsecondary assignment management system 216 can control when a userdevice has receives an access code. Subsequently, user device 210 cantransmit the access code to site controller 712, which can communicatewith primary assignment management system 214 to determine whether thecode is verified, as in FIG. 10A.

In FIG. 10D, many communications parallel those depicted in FIG. 10A-C.However, in this instance—while primary assignment management system 214manages tokens, it does not manage access codes. Rather, secondaryassignment management system 216 or a remote system can manage accesscodes (e.g., via an access code data store 1020 b).

In response to receiving an assignment request, secondary assignmentmanagement system 216 can communicate token data to primary assignmentmanagement system 214, which can ensure (for example) that a status ofthe token is valid. For example, a token may have become invalid due toanother system having used the same or a corresponding token and/or thetoken having been used a threshold number (e.g., a specified number thatis more than one) of times. Primary assignment management system 214 canconvey the status of the token to secondary assignment management system216.

When a status indicates that a token is still valid and represents anability to assign an access code, secondary assignment management system216 may then generate or retrieve an access code that corresponds to thetoken. That access code can be transmitted to user device 210, forexample, immediately, at a defined delay, or upon detecting that a timethreshold defined based on a resource-associated time has passed. Whensite controller 712 receives the access code, a verificationcommunication exchange can be conducted between site controller 712 andsecondary assignment management system 216.

FIG. 11 illustrates a flowchart of an embodiment of a process 1100 forconditionally transmitting access codes. Some or all of process 1100 maybe performed (for example) by an access management system and/or primaryassignment management system. In some instances, process 1100 isperformed in a distributed manner, with different systems (e.g., aprimary assignment management system and a secondary assignmentmanagement system) performing at least part of process 1100.

Process 1100 begins at block 1105, where a credential is authenticatedat a first system (e.g., a primary assignment management system). Thecredential is one associated with a communication received at the firstsystem from a second system (e.g., a secondary assignment managementsystem). The credential can include one, for example, included in thecommunication and/or in metadata associated with the communication. Thecredential may pertain to an identifier of the second system and/orassociated entity. The credential may include, for example, a name,alphanumeric code, or email address. The credential may correspond todata automatically detected at the second system and/or datacorresponding to input provided at the second system. It will beappreciated that the second system or another system (e.g., a thirdsystem) can be configured to provide one or more access-enabling codesto data requesting systems. However, if the third system, for example,is determined to be unreliable, a status can be stored indicating such,and the third system can be prohibited from providing or assigning theone or more access-enabling codes to data requesting systems. See U.S.Ser. No. 14/617,765, filed on Feb. 9, 2015, the disclosure of which ishereby incorporated by reference in its entirety for all purposes. Itwill also be appreciated that an indication can be stored that indicateshow the one or more access-enabling codes are to be allocated to atleast two different distribution channels (e.g., systems). See U.S. Ser.No. 12/435,972, filed on May 5, 2009, the disclosure of which is herebyincorporated by reference in its entirety for all purposes.

Authenticating the credential may include, for example, determining thatthe credential matches or otherwise corresponds to one in a credentialor account data store. The credential or account data store can includeone that is maintained so as to represent or include credentialsassociated with systems or entities for which (for example) a prescribedpayment has been received, a human-authorization technique has beenpassed, an electronic agreement has been accepted (e.g., committing topurchase a specified number or requested access rights), and so on. Atblock 1110, a resource and an resource-access characteristic areidentified. The resource and/or resource-access characteristic may beones specified in the communication and/or may be identifiedautomatically (e.g., as ones corresponding to an above-threshold numberof percentage of access rights with an unassigned status). Thecharacteristic may include, for example, a location identifier and/orprice characteristic (e.g., value, range or threshold).

At block 1115, a secure token is generated based on or to correspondwith an entity associated with the second system, the resource and theresource-access characteristic. In some instances, the secure tokenincludes a set of values (e.g., which may be encoded, converted orencrypted), where a value represents each of the second system, resourceand resource-access characteristic. In some instances, the secure tokendoes not include data that itself is informative as to which entity,resource and/or resource-access characteristic it pertains but cannonetheless correspond to such information via (for example) associatingthe token (e.g., which may be generated using a pseudo-random selectiontechnique and/or application of one or more constraints, such as lengthspecifications or thresholds) with identifiers of the information in adata structure. The secure token may include an alphanumeric code andmay be encrypted or otherwise transformed (e.g., using a key and/ortransformation technique that is accessible to the second system).

In one instance, the secure token is generated based on or to correspondwith the resource-access characteristic by virtue of being generatedbased on or to correspond with one or more access rights having thecharacteristic. As one example, each access right for a resource that isassociated with the characteristic can be identified and associated witha single or with multiple tokens. As another example, an incompletesubset (e.g., corresponding to a quantity specified in thecommunication, a single access right or a defined number or percentage)can be identified and associated with a single or multiple tokens.

At block 1120, the secure token is transmitted to the second system. Insome instances, a given token is transmitted to only one second system(e.g., and other tokens that may correspond to a same access rightand/or resource-access characteristic or to a different access rightand/or resource-access characteristic may be transmitted to other secondsystems). In some instances, a given token is transmitted to multiplesystems, the multiple systems including the second system.

At block 1125, the secure token is received from the second system.Receipt of the token may correspond to, for example, an indication thatan access right corresponding to the token is to be assigned, a requestthat a corresponding access right be assigned, and/or a request for astatus of a corresponding access right. A communication from the secondsystem that includes the token can also include other information, suchas assignment data and/or a commitment to pay a fee for an assignment.For example, assignment data may identify a third device and/or user(e.g., via a username, email address, etc.) that is to be associatedwith an assignment of a corresponding access right.

At block 1130, the resource and resource-access characteristic areidentified. For example, data may be extracted from the token (e.g., byidentifying values corresponding to particular positions within thetoken and/or with particular claim names or fields). As another example,the token (or part of the token) may be used to query a data store foran identifier of each of the resource and the resource-accesscharacteristic. In some instances, a token may need to be transformedprior to or as part of the identification. For example, a received tokenmay be decrypted using a key.

At block 1135, it is determined whether the token corresponds to thesecond system. For example, data may be extracted from the token (e.g.,by identifying a value corresponding to particular positions within thetoken and/or with a particular claim name or field), and the data may beindicative of a system or entity that was or is to be associated withthe token. As another example, the token (or part of the token) may beused to query a data store for an identifier of a system or entity thatwas or is to be associated with the token. As yet another example, thedetermination may be made using non-token data, such as an IP addresscorresponding to a token-inclusive communication or other data in thetoken-inclusive communication. It may be useful to identify the system,for example, when a return communication is to be sent (e.g., thatincludes the access code), when assignment-facilitation data is tracked(e.g., to identify the systems facilitating access-right assignment),and/or when payment is to be collected from a the system facilitatingaccess-right assignment.

At block 1140, it is determined whether one or more access rightscorresponding to the resource and resource-access characteristic areavailable. For example, the determination can include determiningwhether a status of the token indicates that it has not yet been used.As another example, the determination can include identifying one, moreor each access right that corresponds to the token and determiningwhether any of the access rights is available (or have been assigned orare on hold).

When it is determined that no access right corresponding to the token(e.g., to those specifically associated with the token or that matchidentifications associated with the token, such as a resource andresource-access characteristic) is available, then, at block 1145, acommunication may be transmitted to the second system or to a thirddevice (e.g., having been identified in a token-associatedcommunication) that indicates that the token is invalid and/or that nocorresponding access right is available.

When it is determined that an access right corresponding to the token(e.g., to those specifically associated with the token or that matchidentifications associated with the token, such as a resource andresource-access characteristic) is available, then, at block 1150, acommunication may be transmitted to the second system or to a thirddevice (e.g., having been identified in a token-associatedcommunication) that identifies an access code corresponding to theaccess right. For example, if a token is associated with a section 3 forevent X, then an access code transmitted at block 1150 may include anyseat in section 3 for the event. As another example, if a token isassociated with a particular seat for the event, the access code mayinclude the access code for that particular seat. The access code may betransmitted, for example, immediately upon the determination, at adefined time, after detecting that a threshold time prior to aresource-associated time has elapsed, or upon receiving a request (e.g.,from the second system or third device) for the code.

It will be appreciated that, while process 1100 depicts an instancewhere a single access code is transmitted and associated with a token,the process may be extended to relate to multiple access codes pertoken. For example, a token may be generated based on or to correspondto a quantity of access rights. In instances where a token is notassociated with specific access rights, an identification of accessrights (e.g., to determined availability and potentially identify accesscodes) can be performed so as to identify access rights that areassociated with contiguous location characteristics.

Specific details are given in the above description to provide athorough understanding of the embodiments. However, it is understoodthat the embodiments can be practiced without these specific details.For example, circuits can be shown in block diagrams in order not toobscure the embodiments in unnecessary detail. In other instances,well-known circuits, processes, algorithms, structures, and techniquescan be shown without unnecessary detail in order to avoid obscuring theembodiments.

Implementation of the techniques, blocks, steps and means describedabove can be done in various ways. For example, these techniques,blocks, steps and means can be implemented in hardware, software, or acombination thereof. For a hardware implementation, the processing unitscan be implemented within one or more application specific integratedcircuits (ASICs), digital signal processors (DSPs), digital signalprocessing devices (DSPDs), programmable logic devices (PLDs), fieldprogrammable gate arrays (FPGAs), processors, controllers,micro-controllers, microprocessors, other electronic units designed toperform the functions described above, and/or a combination thereof.

Also, it is noted that the embodiments can be described as a processwhich is depicted as a flowchart, a flow diagram, a data flow diagram, astructure diagram, or a block diagram. Although a flowchart can describethe operations as a sequential process, many of the operations can beperformed in parallel or concurrently. In addition, the order of theoperations can be re-arranged. A process is terminated when itsoperations are completed, but could have additional steps not includedin the figure. A process can correspond to a method, a function, aprocedure, a subroutine, a subprogram, etc. When a process correspondsto a function, its termination corresponds to a return of the functionto the calling function or the main function.

Furthermore, embodiments can be implemented by hardware, software,scripting languages, firmware, middleware, microcode, hardwaredescription languages, and/or any combination thereof. When implementedin software, firmware, middleware, scripting language, and/or microcode,the program code or code segments to perform the necessary tasks can bestored in a machine readable medium such as a storage medium. A codesegment or machine-executable instruction can represent a procedure, afunction, a subprogram, a program, a routine, a subroutine, a module, asoftware package, a script, a class, or any combination of instructions,data structures, and/or program statements. A code segment can becoupled to another code segment or a hardware circuit by passing and/orreceiving information, data, arguments, parameters, and/or memorycontents. Information, arguments, parameters, data, etc. can be passed,forwarded, or transmitted via any suitable means including memorysharing, message passing, ticket passing, network transmission, etc.

For a firmware and/or software implementation, the methodologies can beimplemented with modules (e.g., procedures, functions, and so on) thatperform the functions described herein. Any machine-readable mediumtangibly embodying instructions can be used in implementing themethodologies described herein. For example, software codes can bestored in a memory. Memory can be implemented within the processor orexternal to the processor. As used herein the term “memory” refers toany type of long term, short term, volatile, nonvolatile, or otherstorage medium and is not to be limited to any particular type of memoryor number of memories, or type of media upon which memory is stored.

Moreover, as disclosed herein, the term “storage medium”, “storage” or“memory” can represent one or more memories for storing data, includingread only memory (ROM), random access memory (RAM), magnetic RAM, corememory, magnetic disk storage mediums, optical storage mediums, flashmemory devices and/or other machine readable mediums for storinginformation. The term “machine-readable medium” includes, but is notlimited to portable or fixed storage devices, optical storage devices,wireless channels, and/or various other storage mediums capable ofstoring that contain or carry instruction(s) and/or data.

While the principles of the disclosure have been described above inconnection with specific apparatuses and methods, it is to be clearlyunderstood that this description is made only by way of example and notas limitation on the scope of the disclosure.

What is claimed is:
 1. A resource management system for generating andtransmitting tokens associated with resources, the resource managementsystem comprising: a communication engine comprising a processor,wherein the processor is configured to: receive a first credentialassociated with a first system by the first system; generate a firsttoken in response to receiving the first credential; transmit the firsttoken to the first system; receive a second credential associated with asecond system by the second system; generate a second token in responseto receiving the second credential, wherein the first token and thesecond token are associated with an access right to access a resource;transmit the second token to the second system, wherein: the firstsystem is configured to allocate the access right to a first user basedon the first token, and the second system is configured to allocate theaccess right to a second user based on the second token; receive acommunication from the first system regarding establishing a priority toaccess to the resource to the first user; inhibit allocation of thesecond token by the second system to the second user based on thecommunication from the first system; and transmit an access-enablingcode to the first system, wherein the access-enabling code providesaccess to the resource.
 2. The resource management system according toclaim 1, wherein the processor is further configured to: authenticatethe first credential and the second credential based on information ofthe first system and the second system stored in a storage device; andgenerate the first token and the second token in response toauthenticating the first credential and the second credential.
 3. Theresource management system according to claim 1, wherein, to generatethe first token, the processor is further configured to: identify a keyavailable to the first system; generate a first claim value that isindicative of an event; generate a second claim value that is indicativeof a characteristic for accessing the event; generate an alphanumericstring as the first token that includes the first claim value and thesecond claim value; and encrypt the first token using the key.
 4. Theresource management system according to claim 1, wherein the first tokenincludes an expiry date or time, and the processor is further configuredto: transmit an expiration communication to the first system indicatingthat the first token has been expired; and update a token data store tochange a status of the first token as expired.
 5. The resourcemanagement system according to claim 1, wherein the processor is furtherconfigured to: transmit the first token to the first system at a firsttime; receive the first token from the first system at a second timelater than the first time, wherein the first system has received requestfrom the first user to assign the access right to the resource; identifythe resource corresponding to the first token after receiving the firsttoken at the second time; determine that the first token corresponds tothe first system; and transmit the access-enabling code to the firstsystem in response to determining that the first token corresponds tothe first system.
 6. The resource management system according to claim1, wherein the processor is further configured to access a look up tableto identify the access-enabling code corresponding to the first token.7. The resource management system according to claim 1, furthercomprising the first system, wherein the first system is configured to:transmit specifications of the resource to a user device associated withthe first user; receive selection of the resource and intention of thefirst user to establish the priority to access the resource from theuser device; and transmit, to the communication engine, thecommunication regarding establishing the priority to access to theresource to the first user based on the selection of the resource. 8.The resource management system according to claim 7, wherein the firstsystem is further configured to: collect payment information from theuser device; and authorize the payment information before transmittingthe communication to the communication engine.
 9. The resourcemanagement system according to claim 1, wherein the processor is furtherconfigured to: detect that a user device associated with the first useris within a prescribed geographical area associated with the resource;detect a lapse of a threshold time from a time of entrance of the userdevice within the prescribed geographical area; and transmit theaccess-enabling code to the first system based on the lapse of thethreshold time.
 10. A resource management method, by a communicationengine, for generating and transmitting tokens associated withresources, the resource management method comprising: receiving a firstcredential associated with a first system by the first system;generating a first token in response to receiving the first credential;transmitting the first token to the first system; receiving a secondcredential associated with a second system by the second system;generating a second token in response to receiving the secondcredential, wherein the first token and the second token are associatedwith an access right to access a resource; transmitting the second tokento the second system, wherein: the first system is configured toallocate the access right to a first user based on the first token, andthe second system is configured to allocate the access right to a seconduser based on the second token; receiving a communication from the firstsystem regarding establishing a priority to access to the resource tothe first user; inhibiting allocation of the second token by the secondsystem to the second user based on the communication from the firstsystem; and transmitting an access-enabling code to the first system,wherein the access-enabling code provides access to the resource. 11.The resource management method according to claim 10, furthercomprising: authenticating the first credential and the secondcredential based on information of the first system and the secondsystem stored in a storage device; and generating the first token andthe second token in response to authenticating the first credential andthe second credential.
 12. The resource management method according toclaim 10, further comprising: identifying a key available to the firstsystem; generating a first claim value that is indicative of an event;generating a second claim value that is indicative of a characteristicfor accessing the event; generating an alphanumeric string as the firsttoken that includes the first claim value and the second claim value;and encrypting the first token using the key.
 13. The resourcemanagement method according to claim 10, wherein: the first tokenincludes an expiry date or time, and the resource management methodfurther comprising: transmitting an expiration communication to thefirst system indicating that the first token has been expired; andupdating a token data store to change a status of the first token asexpired.
 14. The resource management method according to claim 10,further comprising: transmitting the first token to the first system ata first time; receiving the first token from the first system at asecond time later than the first time, wherein the first system hasreceived request from the first user to assign the access right to theresource; identifying the resource corresponding to the first tokenafter receiving the first token at the second time; determining that thefirst token corresponds to the first system; and transmitting theaccess-enabling code to the first system in response to determining thatthe first token corresponds to the first system.
 15. The resourcemanagement method according to claim 10, further comprising accessing alook up table to identify the access-enabling code corresponding to thefirst token.
 16. The resource management method according to claim 10,further comprising: detecting that a user device associated with thefirst user is within a prescribed geographical area associated with theresource; detecting a lapse of a threshold time from a time of entranceof the user device within the prescribed geographical area; andtransmitting the access-enabling code to the first system based on thelapse of the threshold time.
 17. A computer-program product tangiblyembodied in a non-transitory machine-readable storage medium, includinginstructions configured to cause a communication engine of a resourcemanagement system to perform operations including: receiving a firstcredential associated with a first system by the first system;generating a first token in response to receiving the first credential;transmitting the first token to the first system; receiving a secondcredential associated with a second system by the second system;generating a second token in response to receiving the secondcredential, wherein the first token and the second token are associatedwith an access right to access a resource; transmitting the second tokento the second system, wherein: the first system is configured toallocate the access right to a first user based on the first token, andthe second system is configured to allocate the access right to a seconduser based on the second token; receiving a communication from the firstsystem regarding establishing a priority to access to the resource tothe first user; inhibiting allocation of the second token by the secondsystem to the second user based on the communication from the firstsystem; and transmitting an access-enabling code to the first system,wherein the access-enabling code provides access to the resource. 18.The computer-program product according to claim 17, further comprising:authenticating the first credential and the second credential based oninformation of the first system and the second system stored in astorage device; and generating the first token and the second token inresponse to authenticating the first credential and the secondcredential.
 19. The computer-program product according to claim 17,further comprising: identifying a key available to the first system;generating a first claim value that is indicative of an event;generating a second claim value that is indicative of a characteristicfor accessing the event; generating an alphanumeric string as the firsttoken that includes the first claim value and the second claim value;and encrypting the first token using the key.
 20. The computer-programproduct according to claim 17, wherein: the first token includes anexpiry date or time, and the operations further comprising: transmittingan expiration communication to the first system indicating that thefirst token has been expired; and updating a token data store to changea status of the first token as expired.